-
Notifications
You must be signed in to change notification settings - Fork 58
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: filter remove all subscription from a peer that is leaving #3267
Conversation
You can find the image built from this PR at
Built from 908cd20 |
6854745
to
cab9cd7
Compare
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.
I think we miss adding new connection to our table.
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.
I would consider not make pushToPeers sequential, but the other seems ok!
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.
Ooh amazing PR! Thanks so much! 🤩
Description
@fbarbu15 reported that
waku-interop-tests
started to fail.The problem appeared when one filter-client completely disconnects, e.g., node shutdown. In this case, the
waku_filter_2/subscriptions.nim
module was still keeping an incorrectConnection
instance.waku/waku_filter_v2/protocol.nim
starts keeping track of the filter-client'sConnection
s inpeerConnections: Table[PeerId, Connection]
waku/waku_filter_v2/protocol.nim
adds a newConnection
when a new message needs to be pushed to filter-client.waku/waku_filter_v2/protocol.nim
listens to filter-client-peer disconnect events, in which case, the previousConnection
object is dropped.Issue
closes: #3263
closes: #3254