Merge pull request #41 from vmware-labs/gzurl/exec_ctx

Wasm Execution Contexts now can be created while another thread is running a Wasm module

CHANGELOG.md

@@ -4,6 +4,14 @@
 
 -
 
+## 0.11.1 (2023/03/31)
+
+- Fixes [#40](https://github.com/vmware-labs/mod_wasm/issues/40), where a new thread could not create a new Wasm execution context while another thread was running a Wasm module. This was only measurable if the execution of the Wasm module was long enough in time or if it took longer than expected (i.e.: I/O issues, infinite loop, etc.). Note that CPU-limited Wasm executions are not implemented yet (see [#9](https://github.com/vmware-labs/mod_wasm/issues/9)).
+
+### `libwasm_runtime.so`
+- Internal refactoring of `execution_ctx.rs` to address [#40](https://github.com/vmware-labs/mod_wasm/issues/40).
+- Updated `cargo.lock` dependencies via `cargo update`.
+
 ## 0.11.0 (2023/03/27)
 
 - In this version, Wasm modules can now return any output type via stdout, including binaries with non UTF-8 bytes sequences or `\0` NULL terminators in the middle.

mod_wasm/modules/wasm/mod_wasm.h

@@ -15,4 +15,4 @@
  */
 #define MOD_WASM_VERSION_MAJOR 0
 #define MOD_WASM_VERSION_MINOR 11
-#define MOD_WASM_VERSION_PATCH 0
+#define MOD_WASM_VERSION_PATCH 1

wasm_runtime/Cargo.toml

@@ -1,6 +1,6 @@
 [package]
 name = "wasm_runtime"
-version = "0.11.0"
+version = "0.11.1"
 edition = "2021"
 authors = ["VMware's Wasm Labs"]
 description = "Wrapper for offering a simple C-API to manage WebAssembly modules via Wasmtime"