-
Notifications
You must be signed in to change notification settings - Fork 265
fix: update go-waku #7105
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
fix: update go-waku #7105
Conversation
|
@AlbertoSoutullo can you please try this PR? It fixed the issue for me locally. |
Jenkins BuildsClick to see older builds (41)
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## develop #7105 +/- ##
============================================
+ Coverage 34.88% 59.66% +24.77%
============================================
Files 807 822 +15
Lines 111424 113515 +2091
============================================
+ Hits 38873 67728 +28855
+ Misses 67666 38917 -28749
- Partials 4885 6870 +1985
Flags with carried forward coverage won't be shown. Click here to find out more. |
|
What I see now is: Which I assume it is expected, and I don't see any logs in the bootstrap node, so it looks ok. Looks like it cannot connect. Also in the nwaku node I see: Looks like it is retrying each minute? Tomorrow will take a deeper look. |
6c3a332 to
a406acd
Compare
a406acd to
f77663f
Compare
f77663f to
a5a22f6
Compare
Fixes:
filterprotocol to the bootstrap node that does not support it #7097Description
Update go-waku to get: