Skip to content
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: refactor filter to react when the remote peer closes the stream #3281

Merged
merged 2 commits into from
Feb 6, 2025

Conversation

Ivansete-status
Copy link
Collaborator

@Ivansete-status Ivansete-status commented Feb 6, 2025

Description

Better control when the remote peer closes the WakuFilterPushCodec stream remotely.
For example, go-waku closes the stream for every received message. On the other hand, js-waku keeps the stream opened. Therefore, we support both scenarios.

Issue

closes #3271

Better control when the remote peer closes the WakuFilterPushCodec
stream remotely.
For example, go-waku closes the stream for every received message.
On the other hand, js-waku keeps the stream opened.
Therefore, we support both scenarios.
Copy link

github-actions bot commented Feb 6, 2025

You can find the image built from this PR at

quay.io/wakuorg/nwaku-pr:3281

Built from aa2632a

@Ivansete-status Ivansete-status marked this pull request as ready for review February 6, 2025 15:12
Copy link
Contributor

@gabrielmer gabrielmer left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, thanks so much!

Copy link
Contributor

@NagyZoltanPeter NagyZoltanPeter left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Awesome! Thank you.
I think it is all good however one time getStreamByPeerIdAndProtocol would be better placed at libp2p switch and dialer level, imho.

@Ivansete-status
Copy link
Collaborator Author

Awesome! Thank you. I think it is all good however one time getStreamByPeerIdAndProtocol would be better placed at libp2p switch and dialer level, imho.

Good point! Something to consider in the future if other projects may benefit from that as well: @richard-ramos

@Ivansete-status Ivansete-status merged commit ce7f09a into master Feb 6, 2025
13 of 14 checks passed
@Ivansete-status Ivansete-status deleted the better-filter-approach branch February 6, 2025 16:21
Ivansete-status added a commit that referenced this pull request Feb 6, 2025
#3281)

Better control when the remote peer closes the WakuFilterPushCodec
stream.
For example, go-waku closes the stream for every received message.
On the other hand, js-waku keeps the stream opened.
Therefore, we support both scenarios.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

bug: nwaku<->gowaku interop tests fail with only one received message push when multiple messages are sent
3 participants