-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Cannot get traces for block 21030627 #12432
Comments
Are there any predictions as to when this problem will be fixed? |
any updates here? or workarounds guys? |
Hello. I am encountering the same issue. Is there any ETA for a fix? Does it affect all release versions? |
try to use
instead of |
I am also experiencing this on version |
Or |
also hitting this, would love a fix, happy to test |
+1 I am encountering this exact issue as well, and would greatly appreciate a fix or workaround. |
I'm curious about this. First, are you one of the devs on Erigon? In many cases, "handling traces in a new way" is not possible. Perhaps I'm just misunderstanding what you're saying. Sorry if so. |
I am not an Erigon dev. I've just faced an issue as others in this thread. I wanted to get traces for block 21030627 but |
For those who have access to update their code, here is an example on how to interchange between trace_replayBlockTransactions and debug_traceBlockByNumber:
vs
Results (just a transaction for this example) are:
vs
As seen above and mentioned by @aliaksei-a, the values from trace_replayBlockTransactions can be found in debug_traceBlockByNumber. This might also give the Erigon devs some pointers on how to fix the bug, since it is not breaking on debug_traceBlockByNumber. |
Also worth pointing out that each result in debug_traceBlockByNumber has a "calls" value to show subtraces, but in trace_replayBlockTransactions you have one flat array for all traces/subtraces. So, you will also need to restructure how you process subtraces. Here is an example in Javascript on how to process the results:
vs
|
System information
Erigon version 2.60.8
Actual behaviour
Execute
Result:
Expected behaviour
Expected response is a list of traces without error.
The text was updated successfully, but these errors were encountered: