Handle gap_epoch_open_pending block status when bootstrapping#4821
Merged
pwojcikdev merged 1 commit intonanocurrency:developfrom Jan 13, 2025
Merged
Conversation
Test Results for Commit 9167393Pull Request 4821: Results Test Case Results
Last updated: 2025-01-08 13:32:51 UTC |
a288a3a to
9167393
Compare
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.
We can't process blocks that have
gap_epoch_open_pendingstatus immediately, but instead need to wait until at least one pending send is available for their account chain. Epoch blocks do not link to the associated send block, so we have no way of pulling the dependency other than randomly sampling the rest of the ledger. Given this the proper behavior when encountering this status is to evict the priority account associated with the epoch open block.