eth/tracers: surface database errors during transaction tracing - #35530
Open
0xSHKWON wants to merge 1 commit into
Open
eth/tracers: surface database errors during transaction tracing#355300xSHKWON wants to merge 1 commit into
0xSHKWON wants to merge 1 commit into
Conversation
0xSHKWON
force-pushed
the
fix-tracer-dberr-surfacing
branch
from
August 13, 2026 09:13
d364cd9 to
75d602d
Compare
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
traceTx never checked statedb.Error(), so a database read fault either produced a plausible but wrong trace, or masqueraded as an execution failure ("insufficient funds" for an account that actually has a balance). Check it before the execution error, the same way doCall already does for eth_call.
Note: traceBlock shares one statedb across a block's transactions, so a single fault now fails the whole call rather than just that transaction — same abort-on-error behavior it already has for other errors.