Skip to content

bug: investigate usage of filter subscriptions on non-fleet nodes #2050

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

Closed
danisharora099 opened this issue Jun 28, 2024 · 1 comment
Closed
Assignees
Labels
bug Something isn't working

Comments

@danisharora099
Copy link
Collaborator

This is an investigation request

Problem

Based on status-im/status-go#5344, it was observed that non-fleet nodes found out using Peer Exchange instability in terms of e2e tests using Filter because of some instability.

Proposed Solutions

  • Investigate if this problem is client-agnostic, by investigation in js-waku
  • Translate results to status-go/go-waku
@danisharora099 danisharora099 added the bug Something isn't working label Jun 28, 2024
@fryorcraken fryorcraken added this to Waku Jun 28, 2024
@danisharora099 danisharora099 moved this to Priority in Waku Jun 28, 2024
@danisharora099 danisharora099 self-assigned this Jun 28, 2024
@danisharora099
Copy link
Collaborator Author

Ah, not required.
Based on status-im/status-go#5344 (comment), it seems that status-go does not filter peers by shards/pubsub topics which seems to be the root cause.

@github-project-automation github-project-automation bot moved this from Priority to Done in Waku Jun 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Archived in project
Development

No branches or pull requests

1 participant