feat: add log printing when peer added and removed table #134
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.
As of now, I don't think there is a major log in Kademlia that certainly can determine that a peer has been added.
The login
'msg': 'peer found'
output, which is called prior to the commit, is only an possibility to add for the peer, and the fact that'rt.PeerAdd()'
, which is actually called when a peer is added, is an empty function makes it difficult to measure the performance of Kademlia.Thus, a simple log-add syntax was added.