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
I'm trying to update my waku-dispatcher library to use @next versions of the waku packages to leverage the reliability work + TWN, but I am hitting some issues - not saying they are caused by js-waku, but I would appreciate some help debugging/resolving them
I see AbortError messages for lightpush and filter
waku:error:light-push Failed to send waku light push request +1ms
AbortError: Read aborted
at AbortSignal.listener (index.ts:119:1)
at AbortSignal.onAbort (index.ts:14:1)
waku:error:filter:v2 Error with receiving pipe +4ms
AbortError: Read aborted
at AbortSignal.listener (index.ts:119:1)
at AbortSignal.onAbort (index.ts:14:1)
I see a big churn of nodes - constant disconnections and reconnections - even from my own nwaku node, which causes Filter to be unusable, since the subscription is rarely actually connected
I can rarely publish a message - getting No stream available or Generic error most of the time
Even if I disable defaultBootstrap and try to only rely on my own node, the situation is basically the same
The main goal of this issue is to figure out if there is explicit cause of this behaviour
What you see most likely is because nodes your are connected to are not TWN nodes and thus they are just getting dropped due to being incompatible with js-waku as you are using defaultBootstrap too.
I was trying to pin to a particular version, but had some dependency issues, so I used waku/sdk@next. Trying with 0.0.27-39f8920.0 - seems to be working better!
Will test a bit more and report back:) Why was it "broken" with @next? When/How is that updated?
This is a support request
Problem
I'm trying to update my
waku-dispatcher
library to use@next
versions of the waku packages to leverage the reliability work + TWN, but I am hitting some issues - not saying they are caused by js-waku, but I would appreciate some help debugging/resolving themAbortError
messages for lightpush and filterNo stream available
orGeneric error
most of the timedefaultBootstrap
and try to only rely on my own node, the situation is basically the sameThe main goal of this issue is to figure out if there is explicit cause of this behaviour
Code: https://github.com/vpavlin/waku-dispatcher/blob/chore/update-js-waku/src/index.ts#L32
The most confusing part of all this is that I also have this simple "demo"
https://app.radicle.xyz/nodes/seed.radicle.garden/rad:zaX2EZZnbcFuMD8EGnsWU4nMeLvF/tree/5882d36643a6f3702667e98c94552602200aef5e/index.html
Which works fine and without issues or disconnections, so there must be probably something wrong in
waku-dispatcher
?Notes
The text was updated successfully, but these errors were encountered: