milen 4f95342036 freezeblocks: fix blockreader last frozen bor span and event ids (#9018) ... During testing we run into a "span 7813 not found (db)" due to a very large unwind (1 million blocks). This is because the block reader's `LastFrozenSpanID` and `LastFrozenEventID` returned results that are not consistent with `FrozenBorBlocks`. The latter is taking into account the existence of `.idx` files while the former 2 functions were not. Note such a large unwind is not likely to happen normally unless there is a bug in our unwind logic or an operator is manually unwinding very far back due to reasons like chain halts (ie mumbai bug problem from few months ago), devel testing or anything else along these lines. Regardless, it exposed the above discrepancy which is best to be fixed.		2023-12-18 19:13:21 +02:00
..
freezeblocks	freezeblocks: fix blockreader last frozen bor span and event ids (#9018)	2023-12-18 19:13:21 +02:00
snap	Enforce blockReader interface (#7737)	2023-06-15 13:11:51 +07:00
snapshotsync.go	added grabbing info about downloaded metadata (#8972)	2023-12-13 21:04:14 +07:00