-
Notifications
You must be signed in to change notification settings - Fork 446
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
js-libp2p@0.37.3 does not support chunks bigger than 2Mb anymore #1343
Labels
need/triage
Needs initial labeling and prioritization
Comments
You scripts are initializing Mplex with default max message size value, you should set it to something higher: |
@Alexis-ROYER |
Thanks for the info @mpetrunic. To compare with the Mplex coming along with js-libp2p@0.36.2 (libp2p-mplex@0.10.7 on my side):
|
Not sure honestly. maybe something was overriding that limit |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Severity:
Low
Description:
When receiving chunks of data bigger than 2Mb from a stream,
Error: message size too large!
errors are raised,while with js-libp2p@0.36.2, we could exchange chunks of 10Mb at least.
Not really an operational problem I guess. Quick workarounds easy to set up.
But depending on the root cause, I can't say on my own whether that problem could hide a bigger one.
Steps to reproduce the error:
Using the scripts attached with #1342, launch the sender (3145728 = 3 * 1024 * 1024):
node libp2p-node.0.37.x.mjs --send=path-to-a-big-file --size=3145728
then launch the receiver:
Error displayed by the receiver:
The text was updated successfully, but these errors were encountered: