-
Notifications
You must be signed in to change notification settings - Fork 248
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
WakuV2 filter debugging and refactor #4042
Comments
Related PR: #4020 Extra debug output has been added. Code analysis has uncovered potential problems that are being addressed in that PR:
|
Update: fixed |
status-go PR build fixed |
Changes in status-go PR #4020 - replace weird callbacks with channels passing Filter objects, thus all |
Created a status-mobile PR to run some client-side tests on: status-im/status-mobile#17344 Fixing status-go mobile build issues that surfaced there. |
After meeting with @richard-ramos and @cammellos it was decided to
|
Added a go-waku PR implementing changes discussed on yesterday's meeting: waku-org/go-waku#762 |
Tiny PR: waku-org/go-waku#766, rebased waku-org/go-waku#762. Need to fix some race condition in Relevant changes for multiple subs and sub-specific unsubscribe have been added to https://github.com/status-im/status-go/pulls/4020. |
Fixed race condition in tests in waku-org/go-waku#762, merged. Updated status-go PR https://github.com/status-im/status-go/pulls/4020 to point to updated go-waku. |
Testing mobile PR status-im/status-mobile#17344, fixing issues discovered there. |
Progress update: status-im/status-mobile#16873 (comment) |
Refactored health checks again, now these a single event loop. |
Merged in #4082 and status-im/status-mobile#17472. There are still issues with community sending, as there is no retry. To be investigated. |
Recent updates:
|
I think it's safe to close for now, will be replaced by more specific issues later on. |
Some of the message deliverability issues listed here (status-im/status-mobile#16873) are related to filter operation.
Investigations have been previously carried out in this issue: status-im/status-mobile#17091 (comment). Seems that in that particular case peer connection between filter server and filter client was dropped and not resurrected for some reason.
This issue exists for the purpose of tracking ongoing investigations.
The text was updated successfully, but these errors were encountered: