Stream: git-wasmtime

Topic: wasmtime / PR #14843 [DO NOT REVIEW] Don't panic when ren...

Wasmtime GitHub notifications bot (Oct 19 2026 at 22:27):

jrandolf edited PR #14843.

Wasmtime GitHub notifications bot (Oct 20 2026 at 01:09):

github-actions[bot] added the label wasmtime:api on PR #14843.

Wasmtime GitHub notifications bot (Oct 21 2026 at 00:29):

jrandolf updated PR #14843.

Wasmtime GitHub notifications bot (Oct 21 2026 at 18:28):

jrandolf updated PR #14843.

Wasmtime GitHub notifications bot (Oct 21 2026 at 18:42):

jrandolf updated PR #14843.

Wasmtime GitHub notifications bot (Oct 21 2026 at 18:44):

jrandolf edited PR #14843:

This is a stopgap for #14811 until wasm-wave can represent maps (bytecodealliance/wasm-tools#2777). wasmtime run --invoke panics when the invoked function returns a value WAVE can't represent, such as a map (or a resource, future, stream or error context), because it prints results through wasm-wave's DisplayValue, which returns a fmt::Error for them.

--invoke now prints results through Val::to_wave, which returns an error for these values since bytecodealliance/wasm-tools#2778, so it reports that error and exits with a failure. Otherwise it prints results exactly as before. The error messages built in ensure_type_val no longer go through DisplayValue either.

bytecodealliance/wasm-tools#2778 is merged but not released yet. Until it is, the last commit points the wasm-tools crates at its branch so CI can build this. That commit gets dropped before this lands.

Passing a map argument to --invoke already fails with an error rather than a panic, but the message (unsupported type <<UNSUPPORTED>>) comes from wasm-wave's parser, so improving it needs a change there.

Wasmtime GitHub notifications bot (Oct 23 2026 at 20:55):

jrandolf updated PR #14843.

Last updated: Oct 31 2026 at 23:03 UTC