*: Bump async-std to v1.6.5 (#7306)
* *: Bump async-std to v1.6.5 Prevent users from using v1.6.4 which faces issues receiving incoming TCP connections. See https://github.com/async-rs/async-std/issues/888 for details. * client/network/src/gossip: Use channel instead of condvar `async_std::sync::Condvar::wait_timeout` uses `gloo_timers::callback::Timeout` when compiled for `wasm32-unknown-unknown`. This timeout implementation does not fulfill the requirement of being `Send`. Instead of using a `Condvar` use a `futures::channel::mpsc` to signal progress from the `QueuedSender` to the background `Future`. * client/network/Cargo.toml: Remove async-std unstable feature * client/network/src/gossip: Forward all queued messages * client/network/gossip: Have QueuedSender methods take &mut self * client/network/gossip: Move queue_size_limit into QueuedSender The `queue_size_limit` field is only accessed by `QueuedSender`, thus there is no need to share it between the background future and the `QueuedSender`. * client/network/gossip: Rename background task to future To be a bit picky the background task is not a task in the sense of an asynchonous task, but rather a background future in the sense of `futures::future::Future`.
Showing
- substrate/Cargo.lock 117 additions, 55 deletionssubstrate/Cargo.lock
- substrate/client/network-gossip/Cargo.toml 1 addition, 1 deletionsubstrate/client/network-gossip/Cargo.toml
- substrate/client/network/Cargo.toml 1 addition, 1 deletionsubstrate/client/network/Cargo.toml
- substrate/client/network/src/gossip.rs 72 additions, 89 deletionssubstrate/client/network/src/gossip.rs
- substrate/client/network/src/gossip/tests.rs 1 addition, 1 deletionsubstrate/client/network/src/gossip/tests.rs
- substrate/client/service/Cargo.toml 1 addition, 1 deletionsubstrate/client/service/Cargo.toml
- substrate/utils/prometheus/Cargo.toml 1 addition, 1 deletionsubstrate/utils/prometheus/Cargo.toml
Please register or sign in to comment