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.

Sign up for GitHub

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

Jump to bottom

fix: prevent redials to the peer with mismatched shards #2013

Open
danisharora099 opened this issue May 14, 2024 · 0 comments
Open

fix: prevent redials to the peer with mismatched shards #2013

danisharora099 opened this issue May 14, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@danisharora099
Copy link
Collaborator

Problem

#1965 seems to suggest that js-waku currently keeps redialing peers, even after there has been a mismatch of shards/metadata protocol

Proposed Solutions

Redials should occur for dial failures, as per the ConnectionManager, but we should prevent redials caused due to shards mismatch.

Notes
@danisharora099 danisharora099 mentioned this issue May 14, 2024
Closed
@fryorcraken fryorcraken added this to Waku May 14, 2024
@weboko weboko moved this to Triage in Waku May 14, 2024
@chair28980 chair28980 moved this from Triage to To Do in Waku May 30, 2024
@chair28980 chair28980 added the enhancement New feature or request label May 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
Waku
Status: To Do
Milestone
No milestone
Development

No branches or pull requests
2 participants
@chair28980 @danisharora099