-
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
eth_call - return an error in case the request is to the pruned block #3152
Comments
Probably because block out of —prune range, but it must return error instead of crush of course |
Thanks for your quick response I see, so does |
Yes, 90k blocks by default. See “erigon —help” part about prune |
@AskAlexSharov shouldn’t we return an error instead of crashing in that case? |
@mandrigin of course, and better user-friendly one |
I will reopen then |
@dmitryselivanov will take this one |
Yep, I will take this one :D |
I cannot reproduce |
considering it closed |
System information
Erigon version:
erigon version 2021.12.3-beta
OS & Version:
Linux erigon-mainnet 5.4.157-1-pve #1 SMP PVE 5.4.157-1 (Mon, 29 Nov 2021 12:01:44 +0100) x86_64 x86_64 x86_64 GNU/Linux
(Ubuntu 20.04.3 LTS running in LXC Container on Proxmox 6.4)Commit hash : 2021.12.3-beta release
Erigon command line:
/usr/local/bin/erigon --datadir /srv --maxpeers 20 --private.api.addr=127.0.0.1:9090 --metrics --pprof --prune htc
Rpcdaemon command line:
/usr/local/bin/rpcdaemon --private.api.addr=127.0.0.1:9090 --datadir /srv --http.addr 0.0.0.0 --http.api=eth,erigon,web3,net,debug,trace,txpool,shh --http.vhosts * --ws
Expected behaviour
eth_call
returns correct data (or explains the reason of the error)Actual behaviour
Steps to reproduce the behaviour
See above. The same call works with higher block numbers. The lowest block where the call succeeds shifts up over time.
Backtrace
The text was updated successfully, but these errors were encountered: