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
Goal is to help the user distinguish if RPCs are failing because:
bad request (user need to fix it for succeeding)
the network (retry later when network is OK)
As of right now, the proxy does not reflect JSON-RPC level errors in its statistics (but it is still seen transparently as an error to the proxy caller of course).
The proxy interpret and act only on errors at lower protocol layers (IP, HTTP), but not at "JSON-RPC" level.
The enhancement is to interpret the JSON-RPC to update the statistic and better reflect the "end result".
From v1.10 release notes:
"You can now convert the sui_sdk::error::Error::RpcError response into a sui_sdk::error::JsonRpcError response to determine whether the error is a client or transient error. After converting, you can inspect the code, message, and data of the error, and use the methods is_call_error, is_client_error, is_execution_error, and is_transient_error. You can find an example of this usage at sui-sdk/examples/json_rpc_errors.rs. Note that transient errors now map to code -32050, and -32001 is reserved for any unknown errors the RPC returns."
Goal is to help the user distinguish if RPCs are failing because:
As of right now, the proxy does not reflect JSON-RPC level errors in its statistics (but it is still seen transparently as an error to the proxy caller of course).
The proxy interpret and act only on errors at lower protocol layers (IP, HTTP), but not at "JSON-RPC" level.
The enhancement is to interpret the JSON-RPC to update the statistic and better reflect the "end result".
Related info: MystenLabs/sui#12989
The text was updated successfully, but these errors were encountered: