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
When running a full node and serving a historical RPC request, the data for an old block or transaction might be pruned. In that case we should throw an error denoting that this data is not available instead of incorrectly using the latest state data.
For more clarity in error messages of RPC responses of full nodes.
Implementation
We need make sure that when historical data is not available a suitable error is captured and thrown, instead of receiving latest state data.
Additionally we may want to use the mode the node is in (full or archive), and if it is full we can preempt the attempt to serve old historical data by immediately returning with an error.
The text was updated successfully, but these errors were encountered:
Throw error in `seekInFiles` if txNum is less than smallest txNum in
files.
Eventually this error needs to be handled by IntrablockState, and
ideally the RPC call layer should check if the data is available to
serve the request, but that will be a feature for later.
Issue: #12977
Co-authored-by: antonis19 <[email protected]>
Rationale
When running a full node and serving a historical RPC request, the data for an old block or transaction might be pruned. In that case we should throw an error denoting that this data is not available instead of incorrectly using the latest state data.
Related issue: #12292
Why should this feature exist?
For more clarity in error messages of RPC responses of full nodes.
Implementation
We need make sure that when historical data is not available a suitable error is captured and thrown, instead of receiving latest state data.
Additionally we may want to use the mode the node is in (full or archive), and if it is full we can preempt the attempt to serve old historical data by immediately returning with an error.
The text was updated successfully, but these errors were encountered: