This repository has been archived by the owner on Nov 15, 2023. It is now read-only.
Get the correct number of connected peers in SyncState
#13700
Merged
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.
Protocol
is not a reliable source for the information of connected peers because it does't have real-time information about the real connectivity state.The way to address this properly would be to refactor
SyncingEngine
andChainSync
, remove duplicate peer counting and return a unifiedSyncState
but I haven't found time for that refactoring yet, hopefully soon.