Fix handling of gap_previous#4696
Merged
pwojcikdev merged 2 commits intonanocurrency:developfrom Aug 8, 2024
Merged
Conversation
clemahieu
previously approved these changes
Aug 7, 2024
clemahieu
pushed a commit
that referenced
this pull request
Aug 8, 2024
* Only handle `gap_previous` for live traffic * Use fwd header
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
3 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.
It seems that the legacy bootstrap interferes with ascending bootstrap when handling
gap_previousblock result. This modifies the check, so that it's only triggered for live traffic (where it indicates that the account has some recent activity but we're still missing dependencies).