alexcrichton opened PR #14673 from alexcrichton:wake-more to bytecodealliance:main:
This commit fixes an issue where when a task is waking up to receive a waitable-set notification it ends up taking its own cancellation event instead. The original waitable-set's event is then stuck and nothing else is woken, where other active waiters should be woken.
<!--
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
-->
alexcrichton requested pchickey for a review on PR #14673.
alexcrichton requested wasmtime-core-reviewers for a review on PR #14673.
:thumbs_up: pchickey submitted PR review.
alexcrichton has enabled auto merge for PR #14673.
alexcrichton added PR #14673 Don't lose waitable-set events when cancellation comes in to the merge queue.
:check: alexcrichton merged PR #14673.
alexcrichton removed PR #14673 Don't lose waitable-set events when cancellation comes in from the merge queue.
Last updated: Oct 31 2026 at 23:03 UTC