dicej opened issue #12187:
Currently,
wasmtime run'sinvoke_componentfunction usesFunc::call_asyncto invoke the function. However, that will only run the guest task until it produces a result, then print that result an exit. Ideally, it would useFunc::call_concurrentinstead, which returns aTaskExitwhich can be used to await the completion of the task, allowing any post-return operations to finish.
dicej edited issue #12187:
Currently,
wasmtime run'sinvoke_componentfunction usesFunc::call_asyncto invoke the function. However, that will only run the guest task until it produces a result, then print that result and exit. Ideally, it would useFunc::call_concurrentinstead, which returns aTaskExitwhich can be used to await the completion of the task, allowing any post-return operations to finish.
alexcrichton added the wasm-proposal:component-model-async label to Issue #12187.
vados-cosmonic commented on issue #12187:
Hey just to check, this was closed by https://github.com/bytecodealliance/wasmtime/pull/12185, right?
vados-cosmonic edited a comment on issue #12187:
Hey just to check, this was resolved by https://github.com/bytecodealliance/wasmtime/pull/12185, right?
alexcrichton commented on issue #12187:
That handled executing the
wasi:cli/runfunction, but this is the follow-up for--invokewhich manually selects a function and invokes it. Effectively this needs to usecall_concurrentand then use the secondTaskExitreturn value
dicej assigned dicej to issue #12187.
Last updated: Jan 09 2026 at 13:15 UTC