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

Debug callTracer incorrect output, but only sometimes #413

Closed
quickchase opened this issue May 24, 2022 · 2 comments
Closed

Debug callTracer incorrect output, but only sometimes #413

quickchase opened this issue May 24, 2022 · 2 comments

Comments

@quickchase
Copy link

System information

Geth version: bor/v0.2.14-stable-10c4e89f/linux-amd64/go1.17
OS & Version: Ubuntu 20.04.3
Commit hash : (if develop)

Expected behaviour

There should be only 2 transactions that are reverted in the results

Actual behaviour

Sometimes there are 3 transaction that are reverted in the results

Steps to reproduce the behaviour

DATA='{
    "jsonrpc": "2.0",
    "method": "debug_traceBlockByHash",
    "params": ["0x988901bd289a103dfb34694019d8335007e4bba3f0ceb27cfd1f8cdf366ce52b", {"tracer":"callTracer", "timeout": "300s"}],
    "id": 0
}'

curl -s -H 'Content-Type: application/json' -d $DATA "http://localhost:8545" | jq . > ./output.json
grep revert output.json | wc -l

The output is usually 2 but sometimes it's 3. I have multiple bor archive nodes and they all behave this same way. You may have to place the node under load to produce the result of 3, I'm not sure. It doesn't make a lot of sense but I can definitely reproduce it by just running the call a bunch of times.

@MysticRyuujin
Copy link
Contributor

Possible it's related to this

ethereum/go-ethereum#23205?

@temaniarpit27
Copy link
Contributor

Please use the latest bor version.
Closing this for now.
Reopen if required

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

No branches or pull requests

3 participants