go-ethereum
go-ethereum copied to clipboard
`era-download` reports all files are stale
When downloading era files, we see many of the following logs:
downloading from https://mainnet.era1.nimbus.team/mainnet-00261-a6f4bfca.era1
10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
/home/lc/.ethereum/geth/chaindata/ancient/era/mainnet-00262-1a75662f.era1 is stale
downloading from https://mainnet.era1.nimbus.team/mainnet-00262-1a75662f.era1
10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
/home/lc/.ethereum/geth/chaindata/ancient/era/mainnet-00263-21bf7eee.era1 is stale
downloading from https://mainnet.era1.nimbus.team/mainnet-00263-21bf7eee.era1
10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
/home/lc/.ethereum/geth/chaindata/ancient/era/mainnet-00264-d41eb83d.era1 is stale
downloading from https://mainnet.era1.nimbus.team/mainnet-00264-d41eb83d.era1
10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
/home/lc/.ethereum/geth/chaindata/ancient/era/mainnet-00265-e7a19561.era1 is stale
downloading from https://mainnet.era1.nimbus.team/mainnet-00265-e7a19561.era1
10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
/home/lc/.ethereum/geth/chaindata/ancient/era/mainnet-00266-4f172aab.era1 is stale
downloading from https://mainnet.era1.nimbus.team/mainnet-00266-4f172aab.era1
It seems like it prints this if the file is either not downloaded or if it was but the hash is different. I think it makes sense to separate these concepts and only print the stale message if the file is downloaded but the hashes don't match.
Im on it. maybe takes couple hours for make PR