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
Therefore, we are apparently creating a new stream for every message that is being sent to the subscribed filter clients.
We need to use the same stream for all messages.
Thanks so much @danisharora099 for such great tool! Super insightful 😍
Waku version
v0.33.1
The text was updated successfully, but these errors were encountered:
Hey there @danisharora099 !
I'm adapting the nwaku tests to the new implementation. Once the tests pass properly I'll set the PR #3198 as ready for review and once merged, I will close that one :D
Problem
While running the following example: https://github.com/waku-org/lab.waku.org/tree/066be09ee11fba01b3c6f8ed0e5966de88225104/examples/experimental/railgun-repro
... against a nwaku node base on Railgun infra, @danisharora099 discovered that we easily reach the limit of max number of streams (see https://github.com/waku-org/js-waku/blob/88e33a90fd2a4de93d4ce0cb99dbd77ff454ef34/packages/core/src/lib/filter/index.ts#L47.)
Therefore, we are apparently creating a new stream for every message that is being sent to the subscribed filter clients.
We need to use the same stream for all messages.
Thanks so much @danisharora099 for such great tool! Super insightful 😍
Waku version
v0.33.1
The text was updated successfully, but these errors were encountered: