[5.0 -> main] P2P: Fix handling of known pending block #494
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
[5.0] P2P: Fix handling of known pending block
linh2931
approved these changes
Aug 7, 2024
greg7mdp
approved these changes
Aug 7, 2024
|
Note:start |
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.
In 5.0, P2P added new protocol version to include start/end range in
notice_message. See AntelopeIO/leap#1215When that was added,
sync_recv_noticewas not updated to use the correct id forverify_catchup. This causes additional handshakes and syncing to resolve syncing up to head.This caused
disaster_recovery_2in spring to not reach syned up state in time for the test to not fail.Resolves #390
Merges
leap/release/5.0intomainincluding AntelopeIO/leap#2401Empty diff since it was backported to 5.0 AntelopeIO/leap#2401
Original spring PR: #484 merged into
mainvia #486