-
Notifications
You must be signed in to change notification settings - Fork 2.6k
*: Update to next libp2p version 0.24.0 #6891
Conversation
Looking at the various dashboards (CPU, memory, message count, ...) I can not tell a significant difference between nodes running 0.23 and 0.24 other than the connection count reduction through libp2p/rust-libp2p#1698.
Wild guess: Might this be related to libp2p/rust-libp2p#1710 which makes libp2p properly pass listen upgrade errors? |
Cargo.lock
Outdated
"libp2p-core", | ||
"libp2p-core 0.20.1", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You've probably forgotten to update a Cargo.toml
somewhere. It seems that we're now using two different versions of libp2p at the same time.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please |
bot merge |
Trying merge. |
For now here to test whether libp2p/rust-libp2p#1698 fixes paritytech/polkadot#1532.Up until libp2pv0.24.0
is released this can serve as a place to collect necessary downstream changes.Update libp2p to v0.24.0.
//CC @romanb @twittner @tomaka