-
Notifications
You must be signed in to change notification settings - Fork 993
feat(share/discovery): persist discovered peers #2210
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
Conversation
I'm not convinced this is necessary outside of the context of saving peers for bootstrapper usage, as I have never seen issues finding peers very quickly once we join the network. In fact, until other errors are fixed, this will probably give the disadvantage that we save bad peers (which is why restarting helps so often) |
Think of this in conjunction with Discard, which filters unhealthy peers. Overtime, discovery will persist only healthiest/closest peers without a need to rediscover |
@@ -109,6 +162,18 @@ func (t *testnet) discovery(opts ...Option) *Discovery { | |||
return disc | |||
} | |||
|
|||
func (t *testnet) borkenDiscovery(opts ...Option) *Discovery { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
typo brokenDiscovery
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It was intentional 😈
Closing until becomes relevant |
Closes #2208