Repository navigation
release: v0.23.0 - #206
Merged
Merged
release: v0.23.0#206
Conversation
The test published an event every 100ms from a client thread under a 300ms response timeout, so any 200ms stall between two writes on a loaded runner timed the stream out and the client read end of stream (exit 13). A pause past the timeout reproduces that exit exactly. Nothing in the wake path or http 0.25's lingering close is involved: the timeout closes the connection before any close the client could race. The client now publishes the first event before the request, so the stream opens with it and its arrival shows the waker is published, replacing the stream_ready poll. Each later event is published once the one before it is on the wire, after a 10ms pause, until the stream has lived three timeouts, and the stream ends when the client marks it done. A stall now has to eat 290ms of the 300ms timeout, not 200ms.
fix(#201): pace the event stream test on its own events
the router's decoders serve path captures and form.typed query values alike, so the public text no longer names the route. the go bench comparator answers the same text.
fix(#169): decoder rejections answer 'invalid parameter'
… 0.25.1 std on ^9.4 and crypto on ^0.26, gitlinks at v9.4.1, v0.26.0 and v0.25.1, with demo and doc/bench/laurel following. http 0.25.1 requires mach 6.5, so the floor moves to ^6.5 and CI seeds v6.5.0.
chore(deps): move to mach-std 9.4.1, mach-crypto 0.26.0 and mach-http 0.25.1
chore(release): 0.23.0
octalide
marked this pull request as ready for review
September 28, 2026 17:05
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Integration merge of dev for 0.23.0. Release commit: #205.