fix: FetchFullBlockRangeFuture doesn't return on bad header #10449
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
fgimenez
requested review from
onbjerg,
gakonst,
DaniPopes,
emhane,
mattsse and
Rjected
as code owners
fgimenez
added
C-bug
emhane
approved these changes
Aug 22, 2024
Rjected
approved these changes
Aug 22, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Prevents
FetchFullBlockRangeFuturefrom returning on a single invalid header on a range so that the remaining potentially valid blocks can be used. The failure is still logged and the peer is reported.This change fixes several hive tests that were timing out, they are removed from the expected failures for both the regular and the experimental engines.