Stream: git-wasmtime

Topic: wasmtime / issue #13269 async: cancellable thread.yield n...

Wasmtime GitHub notifications bot (May 04 2026 at 21:39):

lukewagner opened issue #13269:

This seems low-priority, but test/async/cancellable.wast in the CM repo main branch has a test case that currently fails on dev Wasmtime that I believe should pass. It tests whether thread.yield with cancellable set is directly resumed by subtask.cancel (allowing it to eagerly cancel itself, rather saving a "pending cancellation" that gets delivered some time later). Currently, subtask.cancel returns BLOCKED (-1), which suggests that the cancellable is not being considered.

Wasmtime GitHub notifications bot (May 04 2026 at 21:39):

lukewagner added the bug label to Issue #13269.

Wasmtime GitHub notifications bot (May 21 2026 at 16:14):

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

Wasmtime GitHub notifications bot (May 21 2026 at 16:14):

fitzgen assigned dicej to issue #13269.

Wasmtime GitHub notifications bot (May 21 2026 at 16:14):

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

Wasmtime GitHub notifications bot (May 23 2026 at 23:12):

alexcrichton closed issue #13269:

This seems low-priority, but test/async/cancellable.wast in the CM repo main branch has a test case that currently fails on dev Wasmtime that I believe should pass. It tests whether thread.yield with cancellable set is directly resumed by subtask.cancel (allowing it to eagerly cancel itself, rather saving a "pending cancellation" that gets delivered some time later). Currently, subtask.cancel returns BLOCKED (-1), which suggests that the cancellable is not being considered.

Last updated: Jun 01 2026 at 09:49 UTC