-
Notifications
You must be signed in to change notification settings - Fork 9
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
bug: inconsistent messages on eth-pm #199
Comments
Late/repeated is something already tracked on nwaku side and due to the high traffic from Status (not sure if we have an issue for it Cc @jm-clius). Are messages truly missing or is it the rendering? You mentioned rendering. |
They are missed. Edited the original issue |
This is likely due to usage of Relay in the browser + increased traffic due to Status dogfooding.
In the mean time, do feel free to log the exact occurrences and report to nwaku team so they can investigate the missing messages. |
For the dupe message problem. If a message with same payload is received within gossipsub window (20s), it is dropped. If outside window, it's forwarded and hence dupe. That could be resolved by using the hash in |
Temporarily closed PR waku-org/js-waku#1361 |
Acceptance Criteria
meta
field to avoid duplication (output of 14/WAKU2-MESSAGE: Meta attribute and deterministic hashing js-waku#1208 )waku-org/js-waku#905 is long term solution, does not need to be tracked here.
Bug Description
Messages sent and received on eth-pm seem to be highly inconsistent.
Setup is the message
starting
suffixed with an iterating counter, logged every 5 seconds.It can be seen that messages are skipped when received.
browser 1:
browser 2:
This is possibly related to an upstream bug with relay, and could also be related to waku-org/js-waku#751 waku-org/nwaku#1485 waku-org/nwaku#1485 (comment)
The text was updated successfully, but these errors were encountered: