lighthouse/beacon_node
Divma 31386277c3 Sync wrong dbg assertion ()
## Issue Addressed

Running a beacon node I triggered a sync debug panic. And so finally the time to create tests for sync arrived. Fortunately, te bug was not in the sync algorithm itself but a wrong assertion

## Proposed Changes

- Split Range's impl from the BeaconChain via a trait. This is needed for testing. The TestingRig/Harness is way bigger than needed and does not provide the modification functionalities that are needed to test sync. I find this simpler, tho some could disagree.
- Add a regression test for sync that fails before the changes.
- Fix the wrong assertion.
2021-11-19 02:38:25 +00:00
..
beacon_chain Update Lighthouse Dependencies () 2021-11-18 05:08:42 +00:00
client Update Lighthouse Dependencies () 2021-11-18 05:08:42 +00:00
eth1 Update Lighthouse Dependencies () 2021-11-18 05:08:42 +00:00
genesis Update Lighthouse Dependencies () 2021-11-18 05:08:42 +00:00
http_api Update Lighthouse Dependencies () 2021-11-18 05:08:42 +00:00
http_metrics Update Lighthouse Dependencies () 2021-11-18 05:08:42 +00:00
lighthouse_network Update Lighthouse Dependencies () 2021-11-18 05:08:42 +00:00
network Sync wrong dbg assertion () 2021-11-19 02:38:25 +00:00
operation_pool Add op pool metrics for attestations () 2021-11-01 05:52:31 +00:00
src De-duplicate attestations in the slasher () 2021-11-08 00:01:09 +00:00
store Add API version headers and map_fork_name! () 2021-10-28 01:18:04 +00:00
tests Altair consensus changes and refactors () 2021-07-09 06:15:32 +00:00
timer Update Lighthouse Dependencies () 2021-11-18 05:08:42 +00:00
websocket_server Server sent events () 2020-12-04 00:18:58 +00:00
Cargo.toml Rename eth2_libp2p to lighthouse_network () 2021-10-19 00:30:39 +00:00