Stream: git-wasmtime

Topic: wasmtime / issue #13690 async: missing "in waitable set" ...

Wasmtime GitHub notifications bot (Jun 18 2026 at 17:01):

lukewagner opened issue #13690:

Based on CM/#647, there are already traps for sync {stream,future}.{read,write} if the stream/future is already in a waitable sets, but this PR also added traps for {stream,future}.cancel-{read,write} and subtask.cancel which seem to be necessary for the same reason. test/async/trap-if-sync-and-waitable-set.wast I believe tests this (failing when it hits an unreachable instead of the intended trap).

Wasmtime GitHub notifications bot (Jun 18 2026 at 17:01):

lukewagner added the bug label to Issue #13690.

Wasmtime GitHub notifications bot (Jul 02 2026 at 16:25):

fitzgen added the wasm-proposal:component-model-async label to Issue #13690.

Wasmtime GitHub notifications bot (Jul 08 2026 at 14:45):

alexcrichton closed issue #13690:

Based on CM/#647, there are already traps for sync {stream,future}.{read,write} if the stream/future is already in a waitable sets, but this PR also added traps for {stream,future}.cancel-{read,write} and subtask.cancel which seem to be necessary for the same reason. test/async/trap-if-sync-and-waitable-set.wast I believe tests this (failing when it hits an unreachable instead of the intended trap).

Last updated: Jul 29 2026 at 05:03 UTC