-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
debug_traceCallMany
doesn't return the same result as debug_traceTransaction
#12727
Open
1 task done
Labels
Comments
vaigay
added
C-bug
An unexpected or incorrect behavior
S-needs-triage
This issue needs to be labelled
labels
Nov 21, 2024
vaigay
changed the title
Nov 21, 2024
debug_traceCallMany
doesn't return the same result as debug_Transaction
debug_traceCallMany
doesn't return the same result as debug_traceTransaction
in order to debug this I'd need the raw request objects |
Here is the
Here is the
In the
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Describe the bug
Hi,
StateContext
to the previous block, set theBlockOverrides
to the header information of the minted blockdebug_traceCallMany
with thetracer
set tocallTracer
, I then calldebug_Transaction
with a specific transaction hash to compare the results.0x848bf3d087bcc53205c66a04b5d706d5bc2be0be0472d4afa9d4481eca8edef5
.Steps to reproduce
debug_traceCallMany
is too long so I wrote a test for this case, you can updaterpcUrl
and run the testNode logs
Platform(s)
Linux (x86)
What version/commit are you on?
reth v1.1.2: 496bf0b
What database version are you on?
NA
Which chain / network are you on?
mainnet
What type of node are you running?
Full via --full flag
What prune config do you use, if any?
No response
If you've built Reth from source, provide the full command you used
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: