lighthouse/beacon_node/network/src/sync
Divma 413b0b5b2b Correctly update range status when outdated chains are removed (#2827)
We were batch removing chains when purging, and then updating the status of the collection for each of those. This makes the range status be out of sync with the real status. This represented no harm to the global sync status, but I've changed it to comply with a correct debug assertion that I got triggered while doing some testing.
Also added tests and improved code quality as per @paulhauner 's suggestions.
2021-11-26 01:13:49 +00:00
..
backfill_sync Revert peer DB changes from #2724 (#2828) 2021-11-25 03:45:52 +00:00
range_sync Correctly update range status when outdated chains are removed (#2827) 2021-11-26 01:13:49 +00:00
manager.rs Revert peer DB changes from #2724 (#2828) 2021-11-25 03:45:52 +00:00
mod.rs Implement checkpoint sync (#2244) 2021-09-22 00:37:28 +00:00
network_context.rs Correctly update range status when outdated chains are removed (#2827) 2021-11-26 01:13:49 +00:00
peer_sync_info.rs Rename eth2_libp2p to lighthouse_network (#2702) 2021-10-19 00:30:39 +00:00