fix(streams): bound orphaned admin connections#212
Merged
Conversation
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.
What changed
Why
Bun can report a disconnected response consumer through
ReadableStream.cancel()without aborting the serverRequest, and an intermediary may fail to propagate the downstream disconnect at all. Without a bounded lifetime, repeated admin contexts can accumulate orphaned long-lived streams and eventually exhaust available proxy connections. Idempotent teardown handles observable disconnects immediately; the lease bounds the remaining intermediary-orphan case.Verification
bun test— 6,229 pass, 0 failbun run lintbunx tsc --noEmitbun run build