Closed anthony-near closed 1 year ago
Contextual CI error:
thread 'methods::query::tests::test_contract_execution_error' panicked at 'this is unexpected: ServerError(
HandlerError(
ContractExecutionError {
vm_error: "wasm execution failed with error: MethodResolveError(MethodEmptyName)",
block_height: 63503911,
block_hash: 4vMwedjLwTvGGzW23qJQrbaPmNKxQ3xetKXm6s1o8isP,
},
),
)', src/methods/query.rs:175:9
Looks like https://github.com/near/nearcore/pull/7815 changed things a bit. And got rid of the VMResult
enum that encapsulated the VMOutcome
+ VMError
. And instead just unwrapped that into a Result
from which a VMOutcome
is unwrapped.
For this reason, the string inside the outcome report has changed a little.
-wasm execution failed with error: FunctionCallError(MethodResolveError(MethodEmptyName))
+wasm execution failed with error: MethodResolveError(MethodEmptyName)
@anthony-near, can you update the following lines to exclude the FunctionCallError(..)
wrap:
needed for releasing the relayer used for meta transactions https://github.com/near/pagoda-relayer-rs/pull/1 and cli changes https://github.com/near/near-cli-rs/pull/151
near-primitives
and associated crates to0.16.0
1.19.0
to be compatible withnear-primitives
subdependency versions oftokio
rust-version
to1.67.1
after https://github.com/near/nearcore/pull/8456.