You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When executing a WASM function passing an incorrect number of arguments, the assertion is triggered with the following error message:
java.lang.AssertionError: Expected number of params 2, actual 2
org.graalvm.polyglot.PolyglotException: java.lang.AssertionError: Expected number of params 2, actual 2
at org.graalvm.wasm.nodes.WasmRootNode.moveArgumentsToLocals(WasmRootNode.java:243)
at org.graalvm.wasm.nodes.WasmRootNode.executeWithContext(WasmRootNode.java:160)
at org.graalvm.wasm.nodes.WasmRootNode.execute(WasmRootNode.java:144)
at <wasm> sqlite3__wasm_config_i(Unknown)
at org.graalvm.polyglot.Value.execute(Value.java:930)
The "actual" number of arguments in this message should be 1 and not 2.
selhagani
changed the title
Typo in error message "java.lang.AssertionError: Expected number of params 2, actual 2"
[GR-53444] Typo in error message "java.lang.AssertionError: Expected number of params 2, actual 2"
Apr 15, 2024
Describe the issue
When executing a WASM function passing an incorrect number of arguments, the assertion is triggered with the following error message:
The "actual" number of arguments in this message should be 1 and not 2.
This is a typo on the line
graal/wasm/src/org.graalvm.wasm/src/org/graalvm/wasm/nodes/WasmRootNode.java
Line 251 in 62b2745
args.length
should be replaced withWasmArguments.getArgumentCount(args)
).Describe GraalVM and your environment:
The text was updated successfully, but these errors were encountered: