Skip to content

Conversation

@ascjones
Copy link
Collaborator

Error information was missing the error chain, and only displaying the context message:

image

This PR use the Debug impl to display the error chain with the cause:

image

@athei
Copy link
Contributor

athei commented Jan 30, 2023

Okay I don't want to shave the yak here but can you do the same for RPC error? I tried to submit an extrinsic which was tot heavy for the block. The only thing I get back is:

ERROR: Rpc error: RPC error

Probably something directly coming back from subxt. There should be more information. It is the same error whether your extrinsic is invalid or you URL is wrong or missing. This is very confusing.

@SkymanOne
Copy link
Contributor

Any chance we can nicely format the error put and avoid?

... exited with error: error: ...

@ascjones
Copy link
Collaborator Author

Okay I don't want to shave the yak here but can you do the same for RPC error? I tried to submit an extrinsic which was tot heavy for the block. The only thing I get back is:

ERROR: Rpc error: RPC error

Probably something directly coming back from subxt. There should be more information. It is the same error whether your extrinsic is invalid or you URL is wrong or missing. This is very confusing.

Indeed this something with the subxt::Error. Certainly it used to display at least some unstructured information for an invalid transaction. Needs more investigation so won't do it as part of this PR. See #934

@ascjones ascjones merged commit 049e46f into master Jan 31, 2023
@ascjones ascjones deleted the aj/print-error-cause branch January 31, 2023 21:22
@SkymanOne SkymanOne mentioned this pull request Feb 1, 2023
@ascjones ascjones mentioned this pull request Feb 14, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants