-
Notifications
You must be signed in to change notification settings - Fork 248
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 libp2p to 0.53.1 #2212
Update libp2p to 0.53.1 #2212
Conversation
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.
It looks OK. However, I would recommend to postpone the merge of this PR until we stabilize gemini-3g
, otherwise we introduce a whole new line of issues connected to the new libp2p
version. Another issue of this PR, that is shouldn't target the connected-peers
protocol change PR. These changes should be separated.
It would be if there wasn't any merge conflicts otherwise and I don't see why we shouldn't merge connected-peers PR anyway. |
73874a0
to
41c9880
Compare
738d8c2
to
c26af09
Compare
Rebased on |
c26af09
to
38353ae
Compare
Same stuff as before, just rebased on |
Converting to draft, caught following panic locally:
|
There were a few nice bug fixes according to change logs |
This doesn't seem to help with networking issues in the end, but we have to update to it at some point, so why not now, right?
There were a few type changes,
ConnectionHandlerEvent::Close
is gone,ConnectionEvent
is (very annoyingly) non-exhausive (but there are improvements upstream like libp2p/rust-libp2p#4825) and keep-alive mechanism has changed.Interesting changes:
Code contributor checklist: