-
Notifications
You must be signed in to change notification settings - Fork 780
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update dependencies to get rid of the yanked deps #4994
Conversation
Looks like we are waiting on seanmonstar/reqwest#2059 |
There was a patched version of ahash 0.7 all along (see tkaitchuck/aHash#163 (comment)). I just pushed a commit to update to it and now the warnings are gone 😁 |
The |
# Conflicts: # beacon_node/network/src/network_beacon_processor/mod.rs
It turns out the test issue was related to the usage of /// The caller is responsible for ensuring that the listener is in
/// non-blocking mode. Otherwise all I/O operations on the listener
/// will block the thread, which will cause unexpected behavior.
/// Non-blocking mode can be set using [`set_nonblocking`].
Thanks to @michaelsproul for finding and fixing this! 🎉 |
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.
LGTM. Let's merge.
Issue Addressed
#4989
Proposed Changes
The yanked
ahash v0.7.6
andahash v0.8.3
were used by older versions of hashbrown in our depdencies: 0.11.2, 0.12.3. 0.14.0.The following changes have been made:
cargo update -p hashbrown@0.14.0
cargo update -p ahash@0.7.6
hyper
,lru
,serde_yaml
,axum
dep versionstestcontainers
to0.15
as I noticed that there's a new release and we weren't using a release version.