Skip to content

Expose WASM sink memory policy - #100

Open
MesTTo wants to merge 2 commits into
trueagi-io:mainfrom
MesTTo:pr/mork-wasm-memory-policy
Open

Expose WASM sink memory policy#100
MesTTo wants to merge 2 commits into
trueagi-io:mainfrom
MesTTo:pr/mork-wasm-memory-policy

Conversation

@MesTTo

@MesTTo MesTTo commented Jun 23, 2026

Copy link
Copy Markdown
Contributor

Exposes the default Wasmtime linear-memory policy used by the WASM sink and uses that policy when configuring the shared engine.

The policy keeps the current reservation, guard, multi-memory, and signal-trap behavior explicit and testable without changing sink execution semantics.

Depends on #65.

Validation:

  • CARGO_HOME=/home/user/Dev/.cargo-isolated RUSTFLAGS='-C target-cpu=native -Awarnings' cargo +nightly test -p mork wasm_memory_policy --lib
  • CARGO_HOME=/home/user/Dev/.cargo-isolated RUSTFLAGS='-C target-cpu=native -Awarnings' cargo +nightly test -p mork wasm_memory_policy --lib --features wasm
  • CARGO_HOME=/home/user/Dev/.cargo-isolated RUSTFLAGS='-C target-cpu=native -Awarnings' cargo +nightly check -p mork --features wasm
  • git diff --check
  • jscpd --reporters ai --min-lines 8 --min-tokens 80 kernel/src/sinks.rs

@MesTTo
MesTTo force-pushed the pr/mork-wasm-memory-policy branch from ef8ef31 to 1407fe8 Compare July 3, 2026 21:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant