TCP: Don't connect to or log invalid peers #2097
Merged
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
SergiySW
reviewed
Jun 18, 2019
argakiig
pushed a commit
that referenced
this pull request
Jun 27, 2019
* Don't connect to or log invalid peers * Flip terms to improve performance
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.
My log had a lot of Disconnecting from 0.0.0.0... messages. Turns out it's logging as timeout when remote has already closed, thus the endpoint is invalidated. Also prevents connecting to the default endpoint (0.0.0.0:0), which bootstrap_peer returns if there isn't a suitable channel.