feat: add get_in_memory_or_storage_by_tx_range
#11414
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
joshieDo
requested review from
rakita,
shekhirin,
fgimenez,
mattsse and
rkrasiuk
as code owners
fgimenez
approved these changes
Oct 2, 2024
mattsse
approved these changes
Oct 2, 2024
| let provider = self.database.provider()?; | ||
|
|
||
| // Get the last block number stored in the storage which does NOT overlap with in-memory | ||
| // chain. |
There was a problem hiding this comment.
in other words, this ensures that the chain on disk and memory don't overlap but are contiguous
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Our
_by_tx_rangewere only looking into persistent storage and not memory. closes #10182get_in_memory_or_storage_by_tx_range