pchickey opened PR #11018 from bytecodealliance:pch/blocking_write_and_flush to bytecodealliance:main:
See https://github.com/WebAssembly/wasi-io/issues/109
The default implementation of
blocking_write_and_flushcould potentially return a Closed if the stream only becomes Closed upon completion of the flush (returned byflushor the finalcheck_write). We don't want to propogate Closed there as an error, and instead return Ok(()) because the blocking write and its associated flush did succeed. We only want to propagate Errors as surfaced by theflushand finalcheck_writecalls.<!--
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
-->
pchickey requested fitzgen for a review on PR #11018.
pchickey requested wasmtime-core-reviewers for a review on PR #11018.
pchickey requested alexcrichton for a review on PR #11018.
fitzgen submitted PR review.
pchickey merged PR #11018.
Last updated: Dec 06 2025 at 07:03 UTC