style: spell two Durations in their optimal units
New clippy flags duration_suboptimal_units; from_mins(5) and from_secs(1) say what from_secs(300) and from_millis(1000) meant.
This commit is contained in:
@@ -14,7 +14,7 @@ const CONNECT_SWEEP_INTERVAL: Duration = Duration::from_secs(1);
|
||||
/// (peer code 51). Five minutes is what Nicotine+ uses: often enough that a
|
||||
/// queue position on screen means something, rare enough that a peer with a
|
||||
/// long queue is not pestered.
|
||||
const QUEUE_POSITION_INTERVAL: Duration = Duration::from_secs(300);
|
||||
const QUEUE_POSITION_INTERVAL: Duration = Duration::from_mins(5);
|
||||
|
||||
/// How long a write to a child may block. The relay runs under the client
|
||||
/// context lock, so an unbounded write would freeze every other operation
|
||||
|
||||
@@ -4534,7 +4534,7 @@ fn a_queued_download_can_ask_where_it_sits() {
|
||||
ready_rx
|
||||
.recv_timeout(Duration::from_secs(5))
|
||||
.expect("mock peer P connection");
|
||||
std::thread::sleep(Duration::from_millis(1000));
|
||||
std::thread::sleep(Duration::from_secs(1));
|
||||
|
||||
let download_dir = unique_download_dir();
|
||||
let (_download, _status_rx) = client
|
||||
|
||||
Reference in New Issue
Block a user