You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 1, 2021. It is now read-only.
eth_call checks whether we're in beam-sync mode. If we are:
eth_call returns a useful error if you specify a block which is before when we started syncing and also more than 128 blocks behind the tip.
eth_call does what it used to, but it catches MissingAccountTrieNode exceptions and fires off CollectMissingAccount events, once the syncer responds the RPC server retries execution.
What's a good way to test this?
The text was updated successfully, but these errors were encountered:
Some components:
eth_call
checks whether we're in beam-sync mode. If we are:eth_call
returns a useful error if you specify a block which is before when we started syncing and also more than 128 blocks behind the tip.eth_call
does what it used to, but it catchesMissingAccountTrieNode
exceptions and fires offCollectMissingAccount
events, once the syncer responds the RPC server retries execution.What's a good way to test this?
The text was updated successfully, but these errors were encountered: