-
Notifications
You must be signed in to change notification settings - Fork 42
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
chore: upgrade go-libp2p #851
Conversation
Jenkins Builds
|
With the latest go-libp2p, this WARN is being printed:
I opened the following issue libp2p/go-libp2p#2628 to ask about what it means |
ba54a90
to
84c0a61
Compare
This PR has to wait until libp2p/go-libp2p-pubsub#547 is solved. |
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.
Looks good, once the pubsub module is updated we can merge.
libp2p.Muxer("/yamux/1.0.0", yamux.DefaultTransport), | ||
libp2p.Muxer("/mplex/6.7.0", mplex.DefaultTransport), | ||
), | ||
libp2p.DefaultMuxers, |
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.
Looks like mplex was removed by default in latest version.
Maybe we should still enable mplex explicitly so that nodes which don't support yamux still work.
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.
yes
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.
@waku-org/js-waku-developers @waku-org/nwaku-developers shall we move to yamux?
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.
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 think yes, it seems straightforward for js-waku
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.
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.
yes, sounds good.
yamux is recommended to be used over mplex by libp2p -- allows some stream handling enhancements over mplex & is fully supported by js-libp2p
not entirely sure about the compatibility between the two though
PR replaced by #987 |
Description
Upgrades go-libp2p to v0.3.2