-
Notifications
You must be signed in to change notification settings - Fork 265
fix: Crash on uninitialized filterManager #6994
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
Conversation
Jenkins Builds
|
Codecov Report❌ Patch coverage is
❌ Your patch status has failed because the patch coverage (0.00%) is below the target coverage (50.00%). You can increase the patch coverage or adjust the target coverage. Additional details and impacted files@@ Coverage Diff @@
## develop status-im/status-desktop#6994 +/- ##
===========================================
+ Coverage 55.13% 59.42% +4.28%
===========================================
Files 820 821 +1
Lines 116624 116630 +6
===========================================
+ Hits 64301 69305 +5004
+ Misses 45535 40221 -5314
- Partials 6788 7104 +316
Flags with carried forward coverage won't be shown. Click here to find out more.
|
Not sure if this will only hide the root cause because the proper flow on pairing is unknown to me. But from what I've seen Waku is only started after login. While `subscribe` and `unsubscribe` is used in the pairing flow as well.
0bb63b6 to
8000720
Compare
osmaczko
left a comment
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.
Looks harmless, feel free to merge. I'll take it over then and provide a proper fix if needed.
igor-sirotin
left a comment
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.
Let's merge for now and find the actual fix after 👍
I reproduced it with a functional test here: #7002
An attempt to get over this crash #7009. This is based on a superficial investigation to unblock other tasks and I'll merge it only if it's good enough. It's fixing the crash, the synced app seems fine.
Not sure if this will only hide the root cause because the proper flow on pairing is unknown to me. But from what I've seen Waku is only started after login. While
subscribeandunsubscribeis used in the pairing flow as well.