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

feat: Filter error handling and reporting #1101

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

feat: Filter error handling and reporting #1101

chaitanyaprem opened this issue May 14, 2024 · 0 comments

Comments

@chaitanyaprem
Copy link
Collaborator

chaitanyaprem commented May 14, 2024

Problem

As of now filter subscription failures are reported as errors which indicate specific contentTopic failure.
We need to handle reporting subscription failure due to specific reason so that appropriate retry mechanism can be applied.
e.g: If Filter subscribe fails due to filter-limit reached for the peer, then probably a different peer needs to be selected.

TBD: There are more complex cases to consider such as how to indicate this during retry (maybe consider peer exclusion)?

@chaitanyaprem chaitanyaprem self-assigned this May 14, 2024
@fryorcraken fryorcraken added this to Waku May 14, 2024
@chaitanyaprem chaitanyaprem moved this to To Do in Waku May 21, 2024
@chaitanyaprem chaitanyaprem removed their assignment Oct 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: To Do
Development

No branches or pull requests

1 participant