0a4728a241
With checkpoint sync in particular, and state pruning in the future, loading states or state-dependent data may fail. This PR adjusts the code to allow this to be handled gracefully. In particular, the new availability assumption is that states are always available for the finalized checkpoint and newer, but may fail for anything older. The `tail` remains the point where state loading de-facto fails, meaning that between the tail and the finalized checkpoint, we can still get historical data (but code should be prepared to handle this as an error). However, to harden the code against long replays, several operations which are assumed to work only with non-final data (such as gossip verification and validator duties) now limit their search horizon to post-finalized data. * harden several state-dependent operations by logging an error instead of introducing a panic when state loading fails * `withState` -> `withUpdatedState` to differentiate from the other `withState` * `updateStateData` can now fail if no state is found in database - it is also hardened against excessively long replays * `getEpochRef` can now fail when replay fails * reject blocks with invalid target root - they would be ignored previously * fix recursion bug in `isProposed` |
||
|---|---|---|
| .. | ||
| altair | ||
| bellatrix | ||
| phase0 | ||
| README.md | ||
| all_tests.nim | ||
| consensus_spec_tests_preset.nim | ||
| fixtures_utils.nim | ||
| test_fixture_fork_choice.nim | ||
| test_fixture_ssz_generic_types.nim | ||
README.md
Tests based on scenarios generated from the consensus spec.