-
Notifications
You must be signed in to change notification settings - Fork 68
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
IF: replay from before instant-finality transition #2141
Comments
Immediate fix for |
Long term fix: AntelopeIO/spring#7 |
- restart-scenarios-if-test-hard_replay (disabled) requires GH-2141 - restart-scenarios-if-test-none
- terminate-scenarios-if-test-replay (disabled) requires #2141 - terminate-scenarios-if-test-hard_replay
Uncomment test |
IF: Refactor: Move chain_head from fork database back to controller
Moved transition of block_state_legacy to block_state to controller out of fork_database. Changed some fork_db.apply to chain_header apply where fork_db will not be available during replay.
IF: Support replay over instant finality transition
Resolved by #2287 |
When replaying:
nodeos
option--replay-blockchain
we clear state database and replay all blocks including reversible blocks in the fork database. The fork database is opened and consumed before replay. This causes an issue as the fork database needed during replay (until instant-finality transition) requires the legacy fork database. After instant-finality transition, it requires the new fork database.On replay, need to delay consuming the fork database until after all blocks are replayed so the fork database can be opened and consumed in the correct mode with the expected data (
block_state_legacy
vsblock_state
).The following tests current fail and are commented waiting on completion of this task. They should be uncommented in
tests/CMakeLists.txt
and verify they work as part of this effort.nodeos_irreversible_mode_if_lr_test
restart-scenarios-if-test-hard_replay
terminate-scenarios-if-test-replay
terminate-scenarios-if-test-hard_replay
The text was updated successfully, but these errors were encountered: