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
It is possible to catch a thrown JSONRPCError object on failure, but the original error from the request (e.g., over HTTP) is lost, after a number of re-creations of the error during processing. See instances ofnew JSONRPCError in the codebase.
To Reproduce
Steps to reproduce the behavior:
Make a json-rpc request which returns an error.
Observe the returned error object is of the shape:
Describe the bug
It is possible to catch a thrown
JSONRPCError
object on failure, but the original error from the request (e.g., over HTTP) is lost, after a number of re-creations of the error during processing. See instances ofnew JSONRPCError
in the codebase.To Reproduce
Steps to reproduce the behavior:
The original error is not useful as a string, and is effectively two layers deep.
Expected behavior
The error object should be informative of the error encountered, if it is coming from the server (instead of, say, a networking error.)
The text was updated successfully, but these errors were encountered: