-
Notifications
You must be signed in to change notification settings - Fork 1k
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
fix(request-response): don't keep duplicate addresses (v0.52 backport) #4724
fix(request-response): don't keep duplicate addresses (v0.52 backport) #4724
Conversation
This prevents us from adding duplicates into the list of peer addresses we have.
@thomaseizinger Do I change the CHANGELOG too? I'm not too familiar with back porting and releases in this way. |
Yes please. And a version bump! |
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.
I would expect this is missing a version bump in the root Cargo.toml
? Let's see what CI says.
Thanks! |
Think CI did indeed complain. Please hold my hand here, I mess up something each time with these patches. 😉 |
I don't think the "Ensure manifest and changelog" failures for unrelated crates need to be fixed here. Taking a look now. Maybe @thomaseizinger has an idea right away. |
Failures are due to #4714. It touched various files across many crates adding I am adding the |
@mxinden I thought we generally don't try and please CI unnecesarily in backports :) |
Thanks a lot, @mxinden! 🙏 |
Backport of #4700 on
v0.52
branch.