Protect against possible panics in header/horizon sync #2219
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.
Description
Added two missing checks in the header sync and horizon sync.
These checks exit early if the headers/utxo set is aready synchonized or
is ahead of the peer. Previously if this case occurred, the counter iterator
would panic (start > end is invalid).
Motivation and Context
Remove the possibility of a failed assertion (panic) in the base node.
How Has This Been Tested?
Header sync tested with base node.
Types of changes
Checklist:
development
branch.cargo-fmt --all
before pushing.