Michael Sproul ed1fc7cca6 Fix I/O atomicity issues with checkpoint sync (#2671) ... ## Issue Addressed This PR addresses an issue found by @YorickDowne during testing of v2.0.0-rc.0. Due to a lack of atomic database writes on checkpoint sync start-up, it was possible for the database to get into an inconsistent state from which it couldn't recover without `--purge-db`. The core of the issue was that the store's anchor info was being stored _before_ the `PersistedBeaconChain`. If a crash occured so that anchor info was stored but _not_ the `PersistedBeaconChain`, then on restart Lighthouse would think the database was unitialized and attempt to compare-and-swap a `None` value, but would actually find the stale info from the previous run. ## Proposed Changes The issue is fixed by writing the anchor info, the split point, and the `PersistedBeaconChain` atomically on start-up. Some type-hinting ugliness was required, which could possibly be cleaned up in future refactors.		2021-10-05 03:53:17 +00:00
..
src	Fix I/O atomicity issues with checkpoint sync (#2671)	2021-10-05 03:53:17 +00:00
Cargo.toml	Remove unused deps (#2592)	2021-09-30 04:31:42 +00:00