-
Notifications
You must be signed in to change notification settings - Fork 29.2k
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: reduce likelihood of race conditions on keep-alive timeout #54863
Conversation
Review requested:
|
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.
A minor nit but I think it looks fine.
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #54863 +/- ##
==========================================
- Coverage 87.90% 87.89% -0.01%
==========================================
Files 651 651
Lines 183343 183387 +44
Branches 35710 35720 +10
==========================================
+ Hits 161165 161189 +24
- Misses 15466 15469 +3
- Partials 6712 6729 +17
|
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.
The code LGTM.
@ShogunPanda The "changes requested" here was a misclick, I would assume?
Pinging @zanettea as author of original patch.
Also, i'm not sure where does the Co-authored-by
email come from. git log --pretty=format:"Committer: %ce | Author: %ae" 2c3d3832f573fc59baec28d3e6249b055ebfd2b6
shows different addresses (perhaps the author email is the most correct to use here?).
@LiviaMedeiros I grabbed @zanettea's email from one of his repo, but that one is probably incorrect, as github doesn't link back to his account. I'll try these emails and see which one is corrrect. Update: yep, the author email is correct. TIL |
Fixes: nodejs#52649 Refs: nodejs#54293 Co-authored-by: Arrigo Zanette <zanettea@gmail.com>
Thanks for picking up the work, @jazelly! Appreciate it! 🙌 |
Landed in 05ad947 |
This is the continued work from #52653 to fix many similar issues when request is near socket
keepAliveTimeout
threshold. Added 1 second internal timeout to account for network latency for both server and client side.Fixes: #52649
Refs: #54293