Skip to content
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

flatCallTracer returns wrong result instead of error at timeout #29622

Closed
draganm opened this issue Apr 23, 2024 · 0 comments
Closed

flatCallTracer returns wrong result instead of error at timeout #29622

draganm opened this issue Apr 23, 2024 · 0 comments
Labels

Comments

@draganm
Copy link
Contributor

draganm commented Apr 23, 2024

System information

Geth version: geth-1.13.4
CL client & version: lighhouse@lighthouse-5.1.3
OS & Version: Ubuntu 22.04.4 LTS

Expected behaviour

When debug_traceBlockByNumber with flatCallTracer times out, RPC should return an error.

Actual behaviour

Currently debug_traceBlockByNumber with flatCallTracer returns an incorrect trace.

Steps to reproduce the behaviour

  • Perform request with very low timeout to force the issue:
{"method":"debug_traceBlockByNumber","params":["0x12cdbd2",{"timeout":"1ms","tracer":"flatCallTracer"}],"id":0,"jsonrpc":"2.0"}
  • Perform request with very high timeout to obtain the correct trace:
{"method":"debug_traceBlockByNumber","params":["0x12cdbd2",{"timeout":"20s","tracer":"flatCallTracer"}],"id":0,"jsonrpc":"2.0"}
  • compare the outputs

Credit to https://github.com/tsahee for identifying the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant