I've adjusted the WASM error handling to have more specific output that can be sent up to end-users to diagnose the problem with their program, and am using a thread in combination with the wasmtime "increment_engine" approach that enables a rough timeout to be enforced for WASM execution. Bumped the version to 0.6.0 as I feel this is a definite change to original behavior.
I was only able to test this via qemulator package locally, I'll show the tests there.
I've adjusted the WASM error handling to have more specific output that can be sent up to end-users to diagnose the problem with their program, and am using a thread in combination with the wasmtime "increment_engine" approach that enables a rough timeout to be enforced for WASM execution. Bumped the version to 0.6.0 as I feel this is a definite change to original behavior.
I was only able to test this via qemulator package locally, I'll show the tests there.