Wasmtime GitHub notifications bot (Apr 14 2026 at 21:23): Wasmtime GitHub notifications bot (Apr 14 2026 at 21:23):alexcrichton requested dicej for a review on PR #13100.
Wasmtime GitHub notifications bot (Apr 14 2026 at 21:23):alexcrichton opened PR #13100 from alexcrichton:fix-zero-length-cm-async to bytecodealliance:main:
Previously the state of the reader would end up getting corrupted and nothing would be able to make progress. Now the reader is updated back to its original state after the zero-length read/write is complete.
<!--
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 ensure all communication follows the code of conduct:
https://github.com/bytecodealliance/wasmtime/blob/main/CODE_OF_CONDUCT.md
-->
Wasmtime GitHub notifications bot (Apr 14 2026 at 21:25):alexcrichton requested wasmtime-core-reviewers for a review on PR #13100.
Wasmtime GitHub notifications bot (Apr 14 2026 at 22:32):dicej submitted PR review.
Wasmtime GitHub notifications bot (Apr 14 2026 at 22:34):alexcrichton added PR #13100 cm-async: Fix a zero-length write rendezvousing with a zero-length read to the merge queue.
Wasmtime GitHub notifications bot (Apr 14 2026 at 22:58):alexcrichton merged PR #13100.
Wasmtime GitHub notifications bot (Apr 14 2026 at 22:58):alexcrichton removed PR #13100 cm-async: Fix a zero-length write rendezvousing with a zero-length read from the merge queue.
Last updated: May 03 2026 at 22:13 UTC