We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
An example of an actual error field of an RPC response:
error
{"name": "HANDLER_ERROR", "cause": {"info": {}, "name": "INVALID_TRANSACTION"}, "code": -32000, "message": "Server error", "data": {"TxExecutionError": {"InvalidTxError": "Expired"}}}
When fed into JsonProvider.get_error_from_response it raises an exception:
JsonProvider.get_error_from_response
json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0)
The correct behavior would be to return an instance of py_near.exceptions.provider.Expired.
py_near.exceptions.provider.Expired
The text was updated successfully, but these errors were encountered:
Fix pvolnov#16: JSONDecodeError while parsing error messages
50fd6aa
Successfully merging a pull request may close this issue.
An example of an actual
errorfield of an RPC response:{"name": "HANDLER_ERROR", "cause": {"info": {}, "name": "INVALID_TRANSACTION"}, "code": -32000, "message": "Server error", "data": {"TxExecutionError": {"InvalidTxError": "Expired"}}}When fed into
JsonProvider.get_error_from_responseit raises an exception:The correct behavior would be to return an instance of
py_near.exceptions.provider.Expired.The text was updated successfully, but these errors were encountered: