-
Notifications
You must be signed in to change notification settings - Fork 57
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: filter - enhancements in subscription management #3198
base: master
Are you sure you want to change the base?
Conversation
* waku_filter_v2: idiomatic way run periodic subscription manager * filter subscriptions: add more debug logs * filter: make sure the custom start and stop procs are called * make sure filter protocol is started if it is mounted * filter: dial push connection onsubscribe only
You can find the image built from this PR at
Built from 9064bb8 |
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.
Woooow amazing PR! 😍
Thanks so much!
waku/waku_peer_exchange/protocol.nim
Outdated
waku_px_errors.inc(labelValues = [exc.msg]) | ||
callResult = ( | ||
status_code: PeerExchangeResponseStatusCode.SERVICE_UNAVAILABLE, | ||
status_desc: some($exc.msg), | ||
) | ||
finally: | ||
debug "JJJJ" |
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.
We probably need to remove this, although I liked more when we used jamon
for random debug logs 😆
waku/waku_peer_exchange/protocol.nim
Outdated
@@ -272,6 +286,7 @@ proc initProtocolHandler(wpx: WakuPeerExchange) = | |||
).isOkOr: | |||
error "Failed to respond with TOO_MANY_REQUESTS:", error = $error | |||
# close, no data is expected | |||
debug "JJJJ" |
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.
Same here lol
Description
Railgun notified about filter issues. This PR tackled that.
Railgun informed that after 4 days working properly, the nodes stopped sending messages. There were also issues that caused a max of 100 messages being sent over one connection and the reason for that was that we were
dialPeer
ing on every single message the filter server sent to the filter subscribers.Changes
How to test
Issue
closes #3191
closes #3192