-
Notifications
You must be signed in to change notification settings - Fork 53
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: using mplex instead of yamux #2958
Conversation
You can find the image built from this PR at
Built from 559c340 |
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.
Thanks for swift action here. I notice a corresponding issue has been raised in nim-libp2p. Has someone from that team been made aware and are they looking into it?
I just opened the issue, however they have already been informed yesterday through a Discord message Not sure if they started taking a look into it yet, I was waiting a bit to get some kind of answer/update on the new issue and if not ask directly. In any case, I will keep on top of this :)) |
We will need to add back to go-waku support to mplex since go-libp2p dropped support to it. Do you think this is something that we should do soon? or do you think the issue with yamux will be fixed before next nwaku release? |
Oh thank you, I wasn't aware of this. So I will create a thread on the Vac's Will update on how it goes, but won't merge this until we coordinating it with |
It seems that a fix for the leak was found :)) so it seems that we won't need to switch back to |
For your information, the fix is merged (vacp2p/nim-libp2p#1171). |
Closing PR as the leak is fixed in |
Description
Switching our multiplexer from
yamux
tomplex
after finding the Futures leak inyamux
reported in vacp2p/nim-libp2p#1165Once it's taken care of we can switch back to
yamux