-
Notifications
You must be signed in to change notification settings - Fork 30.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
http: destroy timeout socket by Agent #33177
Closed
Closed
Conversation
This file contains 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
nodejs-github-bot
added
errors
Issues and PRs related to JavaScript errors originated in Node.js core.
http
Issues or PRs related to the http subsystem.
labels
Apr 30, 2020
ronag
force-pushed
the
default-timeout-handler
branch
2 times, most recently
from
April 30, 2020 21:06
cbe03f2
to
a55bb98
Compare
ronag
added
the
semver-major
PRs that contain breaking changes and should be released in the next major version.
label
Apr 30, 2020
4 tasks
mcollina
approved these changes
May 2, 2020
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
ronag
force-pushed
the
default-timeout-handler
branch
from
May 3, 2020 16:15
a55bb98
to
b09ba53
Compare
BridgeAR
approved these changes
May 3, 2020
wa-Nadoo
reviewed
May 3, 2020
ronag
force-pushed
the
default-timeout-handler
branch
from
May 4, 2020 04:33
7f1e4fd
to
6084646
Compare
lundibundi
approved these changes
May 5, 2020
Previous location of setting the timeout would override behaviour of custom HttpAgents' keepSocketAlive. Moving it into the default keepSocketAlive allows it to interoperate with custom agents. Fixes: nodejs#33111 PR-URL: nodejs#33127 Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: Robert Nagy <ronagy@icloud.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Juan José Arboleda <soyjuanarbol@gmail.com> Reviewed-By: Andrey Pechkurov <apechkurov@gmail.com>
Co-authored-by: Ruben Bridgewater <ruben@bridgewater.de>
Co-authored-by: Vitaly Kuzmich <wanadoo.by@gmail.com>
ronag
force-pushed
the
default-timeout-handler
branch
from
May 10, 2020 20:18
f6939a0
to
56cae43
Compare
BridgeAR
force-pushed
the
master
branch
2 times, most recently
from
May 31, 2020 12:18
8ae28ff
to
2935f72
Compare
ping @ronag I think this only needs a rebase and is ready otherwise? (it is still a draft) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
errors
Issues and PRs related to JavaScript errors originated in Node.js core.
http
Issues or PRs related to the http subsystem.
semver-major
PRs that contain breaking changes and should be released in the next major version.
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.
Agent must destroy timeout socket when there is no any timeout
handler. Avoid socket hang on forever when the server don't send
any response back.
This is a try at landing #23752 which has become stale.
Checklist
make -j4 test
(UNIX), orvcbuild test
(Windows) passes