Stream: git-wasmtime

Topic: wasmtime / PR #12816 wasi/pipe: fix AsyncReadStream retur...


view this post on Zulip Wasmtime GitHub notifications bot (Mar 21 2026 at 05:23):

vavrusa opened PR #12816 from vavrusa:marek/fix-stream-read-after-closed to bytecodealliance:main:

Hi! This is part of an issue I was trying to debug.

After the inner stream returns 0 the StreamError::Closed is sent to the channel, and after picking it up in read() the stream is set as closed, and the error is returned to the caller.

If the caller however tries to recv() after the socket is closed, AsyncReadStream is going to return empty list and not StreamError::Closed which is ambiguous.

<!--
Please make sure you include the following information:

Our development process is documented in the Wasmtime book:
https://docs.wasmtime.dev/contributing-development-process.html

Please ensure all communication follows the code of conduct:
https://github.com/bytecodealliance/wasmtime/blob/main/CODE_OF_CONDUCT.md
-->

view this post on Zulip Wasmtime GitHub notifications bot (Mar 21 2026 at 05:23):

vavrusa requested wasmtime-wasi-reviewers for a review on PR #12816.

view this post on Zulip Wasmtime GitHub notifications bot (Mar 21 2026 at 08:52):

github-actions[bot] added the label wasi on PR #12816.

view this post on Zulip Wasmtime GitHub notifications bot (Mar 21 2026 at 14:57):

alexcrichton commented on PR #12816:

Thanks! Would it be possible to add a test for this too?


Last updated: Mar 23 2026 at 16:19 UTC