core, core/rawdb: fix transaction indexing #24024
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.
This PR fixes a special corner case in transaction indexing.
When the chain is rewound by
SetHead
to a historical point which is even lower than the transaction indexes tail, then system will reportFailed to decode block body
error all the time, because the relevant blocks are already deleted.In order to avoid this "non-critical-but-annoying" issue, we can recap the indexing target to
head+1
(to is excluded, so it means indexing transactions from 0 to head).