-
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
fix: increasing maxInboundStreams for lightpush from 32 to 100 #2021
fix: increasing maxInboundStreams for lightpush from 32 to 100 #2021
Conversation
size-limit report 📦
|
Thank you @gabrielmer for root causing the issue! I think this config should be set here - js-waku/packages/sdk/src/utils/libp2p.ts Line 69 in e49e728
If you don't mind I can commit to this PR |
I wouldn't set it for all the connections by the node -- when we set it as done by @gabrielmer, we are only changing the value for that particular registrar handler/connection |
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
@weboko @danisharora099 thanks so much! Feel free to modify and commit to the PR in whatever way you feel it improves the solution. |
@weboko merging now, let me know! |
Problem
Solution for waku-org/nwaku#2478 and #1790
Solution
The root cause seems to be in
js-libp2p
, in theDEFAULT_MAX_INBOUND_STREAMS
const defined hereWhen running the test, got the following log
If we configure a higher limit of input streams in
js-libp2p
, the bug is fixedNote
Feel free to recommend cleaner ways to implement the solution. Probably better to have a constant instead of a hardcoded 100, but waiting for the recommendations of the
js-waku
experts 😁