Wasmtime GitHub notifications bot (Jul 15 2025 at 15:04): Wasmtime GitHub notifications bot (Jul 15 2025 at 15:04):alexcrichton added the wasm-proposal:component-model-async label to Issue #11243.
Wasmtime GitHub notifications bot (Jul 15 2025 at 15:04):alexcrichton opened issue #11243:
Currently in the component-model-async implementation all future/stream reads/writes have items moved into a helper task and everything is coordinated via channels. This means that there's no way to cancel an active read/write of a future/stream in a way that the outcome of the cancellation is deterministically known. Cancelling a write may or may not write the values that were previously sent, and cancelling a read may or may not drop a value already read. Supporting this will require new APIs in Wasmtime in addition to new infrastructure within the future/stream implementation.
Wasmtime GitHub notifications bot (Sep 09 2025 at 07:46):rvolosatovs commented on issue #11243:
@alexcrichton @dicej has this been addressed now or is there still work to be done?
Wasmtime GitHub notifications bot (Sep 09 2025 at 13:07):dicej closed issue #11243:
Currently in the component-model-async implementation all future/stream reads/writes have items moved into a helper task and everything is coordinated via channels. This means that there's no way to cancel an active read/write of a future/stream in a way that the outcome of the cancellation is deterministically known. Cancelling a write may or may not write the values that were previously sent, and cancelling a read may or may not drop a value already read. Supporting this will require new APIs in Wasmtime in addition to new infrastructure within the future/stream implementation.
Wasmtime GitHub notifications bot (Sep 09 2025 at 13:07):dicej commented on issue #11243:
AFAIK, yes. I'm going to close this, but feel free to reopen it if appropriate, Alex.
Last updated: Dec 06 2025 at 07:03 UTC