divma 46dbf027af Do not reset batch ids & redownload out of range batches (#1528) ... The changes are somewhat simple but should solve two issues: - When quickly changing between chains once and a second time back again, batchIds would collide and cause havoc. - If we got an out of range response from a peer, sync would remain in syncing but without advancing Changes: - remove the batch id. Identify each batch (inside a chain) by its starting epoch. Target epochs for downloading and processing now advance by EPOCHS_PER_BATCH - for the same reason, move the "to_be_downloaded_id" to be an epoch - remove a sneaky line that dropped an out of range batch without downloading it - bonus: put the chain_id in the log given to the chain. This is why explicitly logging the chain_id is removed		2020-08-18 01:29:51 +00:00
..
src	Do not reset batch ids & redownload out of range batches (#1528)	2020-08-18 01:29:51 +00:00
Cargo.toml	Introduce a queue for attestations from the network (#1511)	2020-08-14 04:38:45 +00:00