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.
refactor(hot): delaminate sharding from HistoryRead/HistoryWrite #68
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Uh oh!
There was an error while loading. Please reload this page.
refactor(hot): delaminate sharding from HistoryRead/HistoryWrite #68
Changes from 1 commit
62e26e0a4c6bb52abf02ff11f229126b511605b07affeb5d8ced36913309fab6e40c7641de571874d57f09ce43b339e87605411054481f8a7583c4ec120b56f785023ec0cb27b22910eae4fb55bebe04d09b42fe322916c3e62adeFile filter
Filter by extension
Conversations
Uh oh!
There was an error while loading. Please reload this page.
Jump to
Uh oh!
There was an error while loading. Please reload this page.
Replace .ok() with .expect("history blocks strictly increasing") on the two BlockNumberList::append calls inside blocks_changed_account and blocks_changed_storage. The error case is only reachable on DB corruption; silently suppressing it would convert corruption into data loss in the read path. Loud panic is correct. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>Uh oh!
There was an error while loading. Please reload this page.
There are no files selected for viewing