Settle HTTP response enqueue failures - #30
Merged
kentbull merged 1 commit intoAug 29, 2026
Merged
Conversation
Abort response production when body output, generator return values, rendered HTTP errors, or terminal chunk framing cannot be accepted by the transport queue. Retain the enqueue failure as the terminal cause and prevent fixed-length byte accounting or producer exhaustion from falsely reporting normal completion.
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
1 participant
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.
Summary
HTTPErroror terminal chunk cannot be enqueuedtcp.Remotersend shutdownWhy
Producer exhaustion or a declared Content-Length is not proof that an HTTP response reached the transport queue.
write()may update response state before enqueue fails, so allowing control to continue can report normal completion for bytes that were never accepted. Enqueue failure must instead become the terminal cause, with no synthesized framing or responder reuse.Tracks ioflo#194. The generic upstream port is deferred behind ioflo#179, ioflo#181, ioflo#191, ioflo#192, and ioflo#193. Real
txCutoffintegration remains release-branch transport work.