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

Return FaultException for invokefunction and invokescript RPC calls #334

Closed
roman-khimov opened this issue Aug 28, 2020 · 0 comments · Fixed by #364
Closed

Return FaultException for invokefunction and invokescript RPC calls #334

roman-khimov opened this issue Aug 28, 2020 · 0 comments · Fixed by #364

Comments

@roman-khimov
Copy link
Contributor

Summary or problem description
This one intersects a little with the recent neo-project/neo#1881. We shouldn't forget about our regular invokescript and invokefunction RPC calls that could also make use of FaultException message. After neo-project/neo#1761, neo-project/neo-node#621 and neo-project/neo-node#630 it is possible to get this additional data for local executions, but not for remote which is a little unbalanced.

Do you have any solution you want to propose?
Add a field containing this message to invoke* calls results.

Where in the software does this update applies to?

  • RPC (HTTP)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant