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
During the last resharding some weird [still unresolved] issue happened on the nearcore regarding the hot/cold storage data transition. And some pieces of the data is missing from a Trie.
This results in an archival node responding with an error similar to
For some reason ReadRPC doesn't know how to serialize this error. We face this errors in those cases when we proxy requests to the native JSON RPC nodes (query.call_function on the *.poolv1.near).
We need to somehow empower ReadRPC with the serialization abitlities around this particular error type to be more clear to the users, since it's hard to understand what does "Failed to serialize JsonRpcError` means.
It's been happening for a long time.
During the last resharding some weird [still unresolved] issue happened on the
nearcore
regarding the hot/cold storage data transition. And some pieces of the data is missing from a Trie.This results in an archival node responding with an error similar to
For some reason ReadRPC doesn't know how to serialize this error. We face this errors in those cases when we proxy requests to the native JSON RPC nodes (
query.call_function
on the*.poolv1.near
).We need to somehow empower ReadRPC with the serialization abitlities around this particular error type to be more clear to the users, since it's hard to understand what does "Failed to serialize JsonRpcError` means.
Step to reproduce
Request (HttPie)
The response is
But has to be
The text was updated successfully, but these errors were encountered: