fix: take lightclient bad peer logic from waku #21458
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Jenkins BuildsClick to see older builds (12)
|
chaitanyaprem
force-pushed
the
fix/filter-bad-peers
branch
2 times, most recently
from
0512114
to
616fb01
Compare
flexsurfer
added
status-go
waku
chaitanyaprem
force-pushed
the
fix/filter-bad-peers
branch
from
616fb01
to
9592da8
Compare
chaitanyaprem
force-pushed
the
fix/filter-bad-peers
branch
from
9592da8
to
62264f2
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
changes mentioned in waku-org/go-waku#1241
A simple logic to delete bad peers based on dial failures so that they don't get reused. this may help stabilize filter subscriptions faster.
..### Testing notes
Platforms
Areas that maybe impacted
network switch
startup of app
bringing to foreground
Functional
Steps to test
status: ready