You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Railgun reported bugs around being able to consistently receive Filter messages for a consistently long duration. The specifics are yet to be understood.
I'm noticing that the peer disconnects after 100 filter messages being received on the edge node (js-waku)
The app has auto re-dial if disconnected, and then it sends another 100 Filter messages and disconnects again
Logs and debugging markers enabled in the app
Run with npm i && npm run dev
The text was updated successfully, but these errors were encountered:
Based on recent improvements done on nwaku, the newer image (harbor.status.im/wakuorg/nwaku:railgun-0.33.1-more-logs) resolves the 100-message cap bug with Filter.
I can validate that the connection does not drop after a 100 incoming Filter messages now.
Problem
Railgun reported bugs around being able to consistently receive Filter messages for a consistently long duration. The specifics are yet to be understood.
Proposed Solution
Currently investigating/TBD
Notes
Wrote a minimal reproducible app for this using the same pubsub topics and content topics as their network: https://github.com/waku-org/lab.waku.org/tree/master/examples/experimental/railgun-repro
I'm noticing that the peer disconnects after 100 filter messages being received on the edge node (js-waku)
The app has auto re-dial if disconnected, and then it sends another 100 Filter messages and disconnects again
Logs and debugging markers enabled in the app
Run with
npm i && npm run dev
The text was updated successfully, but these errors were encountered: