feat(en): Cache blocks in fetch_l2_block
#403
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What ❔
fetch_l2_block
saves blocks in cacheExternalIO:: seal_miniblock
Why ❔
Making cache client to behave traditional way, i.e. cache results got from server. This will also fix invariant that previous block is always (except for first iteration after start) kept in cache and fix sporadic panics caused by inconsistent API responses
Checklist
zk fmt
andzk lint
.