This repository has been archived by the owner on Nov 15, 2023. It is now read-only.
Add more logging to the network #4621
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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
(I hesitated to label this PR as "insubstantial")
Adds more
trace!logging to the network.The most important one is the
Failed to reach ..., which might help figuring out why nodes can't connect to each other. Most of the time the error is going to be either a boring "timeout" or a boring "connection rejected", but sometimes it's a "peer id mismatch", in which case it's important to know.Additionally, we now use the
next_event()method on theSwarm, which guarantees thatNonecannot be returned.