-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
disable mplex stream muxer #7689
Conversation
Codecov Report
@@ Coverage Diff @@
## master #7689 +/- ##
==========================================
- Coverage 39.56% 39.48% -0.09%
==========================================
Files 637 637
Lines 67924 67909 -15
==========================================
- Hits 26877 26811 -66
- Misses 36445 36482 +37
- Partials 4602 4616 +14
Continue to review full report at Codecov.
|
2318f16
to
9739f65
Compare
needs |
9739f65
to
cf0faf5
Compare
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. I like mplex as a simpler fallback, but that simplicity does have a cost which doesn't seem warranted here.
I expect we'll introduce separate "gateway" nodes eventually that might want to enable that transport, but we can cross that bridge later.
Compatibility considerations: The reason we have mplex in IPFS is that js-libp2p doesn't support yamux, so mplex is the fallback stream muxer there. We don't care about js-libp2p in lotus. As far as I know (someone with more ecosystem insight please double check!), all Filecoin implementations support yamux (at least Venus does), so there's no need for a fallback.