Skip to content
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

Using js-waku @next #2112

Closed
vpavlin opened this issue Aug 23, 2024 · 3 comments
Closed

Using js-waku @next #2112

vpavlin opened this issue Aug 23, 2024 · 3 comments
Labels
bug Something isn't working dependencies Pull requests that update a dependency file or issues that track it

Comments

@vpavlin
Copy link
Member

vpavlin commented Aug 23, 2024

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 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

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

@weboko
Copy link
Collaborator

weboko commented Aug 23, 2024

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.

Also, can you make sure you use similar version to waku-org/lab.waku.org@179b501 ?

@vpavlin
Copy link
Member Author

vpavlin commented Aug 23, 2024

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?

@weboko
Copy link
Collaborator

weboko commented Aug 23, 2024

I am not sure why it happens, last @waku/sdk@next is pointing to 0.0.27-39f8920.0
https://www.npmjs.com/package/@waku/sdk?activeTab=versions

It can be due to cache or maybe you were installing it before I published working version.

@weboko weboko closed this as completed Aug 23, 2024
@weboko weboko added bug Something isn't working dependencies Pull requests that update a dependency file or issues that track it labels Aug 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working dependencies Pull requests that update a dependency file or issues that track it
Projects
Status: Done
Development

No branches or pull requests

2 participants