Skip to content
New issue

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

Transaction execution should return a more clear error #2673

Closed
Tracked by #2533 ...
Fraccaman opened this issue Feb 20, 2024 · 2 comments · Fixed by #2958
Closed
Tracked by #2533 ...

Transaction execution should return a more clear error #2673

Fraccaman opened this issue Feb 20, 2024 · 2 comments · Fixed by #2958
Labels
enhancement New feature or request

Comments

@Fraccaman
Copy link
Member

Right now, if a transaction fails, the client reports only which keys have been changed and which VPs have rejected the transaction. This is very confusing for a user as the reason why the transaction was rejected is not clear.
We should add the ability for to return a more clear error from the WASM execution back to the client to inform the user of what when wrong.

@Fraccaman Fraccaman added the enhancement New feature or request label Feb 20, 2024
@cwgoes
Copy link
Collaborator

cwgoes commented Feb 20, 2024

Could we log something from WASM during transaction execution that could be picked up by the VM and then included in the returned message?

@Fraccaman
Copy link
Member Author

yeah something like this but I dont think its so easy to implement.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants