Stream: git-wasmtime

Topic: wasmtime / PR #14843 Don't panic when rendering values WA...

view this post on Zulip Wasmtime GitHub notifications bot (Oct 19 2026 at 19:18):

jrandolf opened PR #14843 from jrandolf:wave-unsupported-no-panic to bytecodealliance:main:

This is a stopgap for #14811 until wasm-wave can represent maps (bytecodealliance/wasm-tools#2777). wasm-wave's writer panics on values whose kind is Unsupported, which wasmtime run --invoke hits for any function returning a map (or a resource, future, stream or error context), and which Val::to_wave hits despite returning a Result.

This checks values before handing them to wasm-wave and returns an error naming the type instead, e.g. cannot render `map` values as WAVE yet. --invoke otherwise prints results exactly as before.

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.

Last updated: Oct 31 2026 at 23:03 UTC