Repository navigation
fix(fetch): retire idle API request connections - #44024
Merged
Merged
Conversation
Yury Semikhatsky (yury-s)
approved these changes
Nov 10, 2026
Yury Semikhatsky (yury-s)
marked this pull request as ready for review
November 10, 2026 02:04
Contributor
Test results for "MCP"5229 passed, 637 skipped Merge workflow run. |
Contributor
Test results for "tests 1"2 flaky23619 passed, 705 skipped Merge workflow run. |
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.
Set the per-context HTTP and HTTPS agent timeout to 5000 ms, matching Node's global agents. Without a timeout, Node does not apply a positive server keep-alive hint, leaving idle connections available for reuse near the server's close deadline.
Extend the existing server-address test to check client-side retirement of an idle connection. The check fails without the fix and passes with it.
Both API request suites passed on Chromium, Firefox and WebKit (613 passed, 2 skipped). Build and flint passed. A response with separate 6-second header and body delays completed successfully.
Fixes #44007
Triaged on Linux by the Playwright bot - agent run