-
Notifications
You must be signed in to change notification settings - Fork 247
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
chore_: bump go-waku fixes on peers and concurrent access #6187
base: develop
Are you sure you want to change the base?
Conversation
Jenkins BuildsClick to see older builds (16)
|
[blocked]: cannot merge up until this is merged: |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## develop #6187 +/- ##
===========================================
+ Coverage 13.89% 14.00% +0.10%
===========================================
Files 817 817
Lines 108311 108311
===========================================
+ Hits 15055 15164 +109
+ Misses 91333 91218 -115
- Partials 1923 1929 +6
Flags with carried forward coverage won't be shown. Click here to find out more. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
Do you know if waku-org/go-waku#1244 been tested?
EDIT: just saw the comment above!
Assuming we can't get waku-org/go-waku#1244 tested & merged, we could try to create a branch in go-waku for 0.32 and only include the changes from waku-org/go-waku#1265 cc: @churik @anastasiyaig |
@richard-ramos can the issues mentioned in this PR cause crashes? |
This one can: waku-org/go-waku#1265 although it seems to happen rarely |
@anastasiyaig @churik |
thats why i ask, i did not face with this issue at all recently :) |
So we have status-im/status-mobile#21799 (comment) based on this comment I suppose it might be the solution to this problem, right? @richard-ramos can you please clarify the regression area for these fixes, what might be affected? Based on description, I'd say app state on network conditions (online/offline/cellular) + fetching messages should work the same. |
ce5d409
to
6b30855
Compare
|
@richard-ramos can we rebase it to |
cc-ing: @plopezlpz as he is the owner of this PR 🚀 |
@plopezlpz could you force a commit hash change in this PR while also changing it to point to the release branch Nevermind @plopezlpz I created a duplicate PR for mobile to experiment. |
@ilmotta @churik @richard-ramos |
bump go-waku including fixes: