-
Notifications
You must be signed in to change notification settings - Fork 645
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
feat (runtime): Wasmer ExceptionCode support #2505
Conversation
…ore into fckt/wasmer-16-update
…ore into fckt/wasmer-16-update
…ore into fckt/wasmer-16-update
…ror cases form Wasmer
…ore into fckt/wasmer-16-update
a4a71b2
to
e5d7efc
Compare
e5d7efc
to
7de946b
Compare
…nearcore into fckt/wasmer-exception-code
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It there a way to have tests for this?
@frol For example, when we'll updated to a fixed Wasmer version this test will fail (since the call will return |
Due to wasmerio/wasmer#1409 we need to rollback Wasmer to older version. I am replacing some of Wasmer generated error with Unknown to avoid undoing too much code from this PR: #2505 After the following PR lands wasmerio/wasmer#1401 we would need to revisit error handling from Wasmer anyway. CC @fckt ### Testing Ran near-evm test. CI passes.
On top of #2332
The PR just adds Wasmer ExceptionCode support, introduced in Wasmer 0.16. Introduces new Tx Error types, so chain/jsonrpc/res/rpc_errors_schema.json updated.
FunctionCallError::WasmUnknownError
introduced.Wasmer never returns ExceptionCode today (at least for a single-pass), that's why tests for traps return
FunctionCallError::WasmUnknownError
.wasmerio/wasmer#1338