Stream: git-wasmtime

Topic: wasmtime / PR #11719 Read `wasmtime serve` output in back...


view this post on Zulip Wasmtime GitHub notifications bot (Sep 19 2025 at 15:50):

alexcrichton opened PR #11719 from alexcrichton:fix-test-hang to bytecodealliance:main:

If wasm traps with RUST_BACKTRACE=1 this produces more output than the OS buffers by default. Output isn't actually read from the server until we're done sending requests, but if multiple requests are sent it may mean that the server gets stuck during a print and is unable to accept more requests. This commit updates output to be read in background threads instead of only when the server is finished.

Closes #11715

<!--
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 (Sep 19 2025 at 15:50):

alexcrichton requested fitzgen for a review on PR #11719.

view this post on Zulip Wasmtime GitHub notifications bot (Sep 19 2025 at 15:50):

alexcrichton requested wasmtime-core-reviewers for a review on PR #11719.

view this post on Zulip Wasmtime GitHub notifications bot (Sep 21 2025 at 14:52):

alexcrichton updated PR #11719.

view this post on Zulip Wasmtime GitHub notifications bot (Sep 22 2025 at 16:18):

pchickey submitted PR review.

view this post on Zulip Wasmtime GitHub notifications bot (Sep 23 2025 at 16:57):

fitzgen submitted PR review.

view this post on Zulip Wasmtime GitHub notifications bot (Sep 23 2025 at 17:49):

fitzgen merged PR #11719.


Last updated: Dec 06 2025 at 07:03 UTC