Optimize light node synchronization logic#4323
Merged
lvs007 merged 3 commits intotronprotocol:release_v4.5.0from Apr 26, 2022
Merged
Optimize light node synchronization logic#4323lvs007 merged 3 commits intotronprotocol:release_v4.5.0from
lvs007 merged 3 commits intotronprotocol:release_v4.5.0from
Conversation
Codecov Report
@@ Coverage Diff @@
## release_v4.5.0 #4323 +/- ##
=================================================
Coverage ? 53.44%
Complexity ? 7700
=================================================
Files ? 813
Lines ? 46354
Branches ? 5049
=================================================
Hits ? 24773
Misses ? 19626
Partials ? 1955 Continue to review full report at Codecov.
|
lvs007
approved these changes
Apr 26, 2022
This file contains hidden or 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 join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
What does this PR do?
Optimize light node synchronization logic.
refer to tronprotocol/tips#388
Why are these changes required?
Make the node quickly find a node that can establish an effective connection, avoid repeatedly connecting invalid nodes, and improve the efficiency of connection establishment.
This PR has been tested by:
Follow up
Extra details