realbigsean 33d01a7911 miscelaneous fixes on syncing, rpc and responding to peer's sync related requests (#3827) ... - there was a bug in responding range blob requests where we would incorrectly label the first slot of an epoch as a non-skipped slot if it were skipped. this bug did not exist in the code for responding to block range request because the logic error was mitigated by defensive coding elsewhere - there was a bug where a block received during range sync without a corresponding blob (and vice versa) was incorrectly interpreted as a stream termination - RPC size limit fixes. - Our blob cache was dead locking so I removed use of it for now. - Because of our change in finalized sync batch size from 2 to 1 and our transition to using exact epoch boundaries for batches (rather than one slot past the epoch boundary), we need to sync finalized sync to 2 epochs + 1 slot past our peer's finalized slot in order to finalize the chain locally. - use fork context bytes in rpc methods on both the server and client side		2022-12-21 15:50:51 -05:00
..
src	miscelaneous fixes on syncing, rpc and responding to peer's sync related requests (#3827)	2022-12-21 15:50:51 -05:00
Cargo.toml	Feature gate withdrawals (#3684)	2022-11-04 16:50:26 -04:00