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
..
beacon_chain	Update Lighthouse Dependencies (#2818)	2021-11-18 05:08:42 +00:00
client	Update Lighthouse Dependencies (#2818)	2021-11-18 05:08:42 +00:00
eth1	Update Lighthouse Dependencies (#2818)	2021-11-18 05:08:42 +00:00
genesis	Update Lighthouse Dependencies (#2818)	2021-11-18 05:08:42 +00:00
http_api	Revert peer DB changes from #2724 (#2828)	2021-11-25 03:45:52 +00:00
http_metrics	Update Lighthouse Dependencies (#2818)	2021-11-18 05:08:42 +00:00
lighthouse_network	Allow additional subnet peers (#2823)	2021-11-25 21:27:08 +00:00
network	Correctly update range status when outdated chains are removed (#2827)	2021-11-26 01:13:49 +00:00
operation_pool	Add op pool metrics for attestations (#2758)	2021-11-01 05:52:31 +00:00
src	De-duplicate attestations in the slasher (#2767)	2021-11-08 00:01:09 +00:00
store	Add API version headers and map_fork_name! (#2745)	2021-10-28 01:18:04 +00:00
tests	Altair consensus changes and refactors (#2279)	2021-07-09 06:15:32 +00:00
timer	Update Lighthouse Dependencies (#2818)	2021-11-18 05:08:42 +00:00
websocket_server	Server sent events (#1920)	2020-12-04 00:18:58 +00:00
Cargo.toml	Rename eth2_libp2p to lighthouse_network (#2702)	2021-10-19 00:30:39 +00:00