Wasmtime GitHub notifications bot (Oct 26 2026 at 23:27): Wasmtime GitHub notifications bot (Oct 26 2026 at 23:27):pchickey edited PR #15002.
Wasmtime GitHub notifications bot (Oct 26 2026 at 23:30):pchickey edited PR #15002:
It turns out that even SIGTERM can be avoided by a looping wasm guest, because in some situations in wasmtime serve it can tokio worker to spin forever when there are no timeouts available to interrupt it.
The options to this are either to make the overhead of epoch mandatory, or to accept that this is a way for a wasm to consume CPU until things escalate to SIGKILL. For wasmtime cli, I think its more valuable to retain the default of running without timeouts, and just document that this is a possible shortcoming.
<!--
Please make sure you include the following information:
If this work has been discussed elsewhere, please include a link to that
conversation. If it was discussed in an issue, just mention "issue #...".Explain why this change is needed. If the details are in an issue already,
this can be brief.Our development process is documented in the Wasmtime book:
https://docs.wasmtime.dev/contributing-development-process.htmlPlease review the Bytecode Alliance's AI tool usage policy at
https://github.com/bytecodealliance/governance/blob/main/AI_TOOL_POLICY.mdPlease ensure all communication follows the code of conduct:
https://github.com/bytecodealliance/wasmtime/blob/main/CODE_OF_CONDUCT.md
-->
Wasmtime GitHub notifications bot (Oct 26 2026 at 23:30):pchickey requested cfallin for a review on PR #15002.
Wasmtime GitHub notifications bot (Oct 26 2026 at 23:32):pchickey updated PR #15002.
Wasmtime GitHub notifications bot (Oct 26 2026 at 23:32):pchickey has marked PR #15002 as ready for review.
Wasmtime GitHub notifications bot (Oct 26 2026 at 23:50):pchickey added PR #15002 wasmtime cli flags: document a guest without a timeout may spin forever to the merge queue.
Wasmtime GitHub notifications bot (Oct 27 2026 at 00:13)::check: pchickey merged PR #15002.
Wasmtime GitHub notifications bot (Oct 27 2026 at 00:13):pchickey removed PR #15002 wasmtime cli flags: document a guest without a timeout may spin forever from the merge queue.
Last updated: Oct 31 2026 at 23:03 UTC