Uh oh!
There was an error while loading. Please reload this page.
[v12.x backport] http: reset headers timeout on headers complete - #35819
[v12.x backport] http: reset headers timeout on headers complete#35819orgads wants to merge 1 commit into
Conversation
nodejs-github-bot
commented
Oct 26, 2020
Review requested:
|
orgads
commented
Oct 26, 2020
Looks like another commit is missing? |
orgads
commented
Oct 26, 2020
The test passed 1000 as 1e3, which is double, not int32. Probably another commit is missing. |
3225d5d to
9828efdCompareFlarna
commented
Oct 26, 2020
Javascript has only Maybe include #34609 in the backport PR as it fixes something in the test added here. |
ronag
commented
Oct 26, 2020
orgads
commented
Oct 26, 2020
The tests pass now (The arguments to |
This comment has been minimized.
This comment has been minimized.
Flarna
commented
Oct 26, 2020
The test fails look like that ones fixed by #34609 |
orgads
commented
Oct 26, 2020
It no longer fails. Unfortunately, the CI keeps running and notifying even after force-push... |
orgads
commented
Oct 26, 2020
Oops, didn't notice the bsd tests. Yes, it looks like it. I'll amend. |
headers timeout should not occur *after* headers have been received. Fixes: nodejs#35661 PR-URL: nodejs#34578 Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: Fedor Indutny <fedor.indutny@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Pranshu Srivastava <rexagod@gmail.com> (cherry picked from commit da4d8de)
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
watilde
commented
Oct 27, 2020
I tested in my local with https://github.com/neversun/node-issue-35661 and this branch works. |
cc @nodejs/releasers |
richardlau
commented
Oct 27, 2020
This needs to be targeted at |
Agreed as I commented the same earlier and I should have arranged that before asking for
|
nodejs-github-bot
commented
Oct 27, 2020
watilde
commented
Oct 30, 2020
I took the fast-track since 48h or more has passed, but I still think this PR remains a high priority as it fixes the regression. cc @nodejs/releasers |
orgads
commented
Nov 2, 2020
What are we waiting for? |
watilde
commented
Nov 2, 2020
Let me cc @nodejs/backporters who can land this commit onto the staging branch. |
MylesBorins
commented
Nov 2, 2020
@watilde we'll review this and all 12.x backports before cutting the RC fwiw fast track isn't necessary for backports as they don't have the same timing requirement as they have previously been reviewed |
codebytere
commented
Nov 2, 2020
Landed in 9f3e888 |
headers timeout should not occur *after* headers have been received. Fixes: #35661 PR-URL: #34578 Backport-PR-URL: #35819 Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: Fedor Indutny <fedor.indutny@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Pranshu Srivastava <rexagod@gmail.com> (cherry picked from commit da4d8de)
watilde
commented
Nov 3, 2020
@MylesBorins Thank you for letting me know it! |
headers timeout should not occur *after* headers have been received. Fixes: #35661 PR-URL: #34578 Backport-PR-URL: #35819 Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: Fedor Indutny <fedor.indutny@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Pranshu Srivastava <rexagod@gmail.com> (cherry picked from commit da4d8de)
headers timeout should not occur after headers have been
received.
Fixes: #35661
PR-URL: #34578
Reviewed-By: Anna Henningsen anna@addaleax.net
Reviewed-By: Fedor Indutny fedor.indutny@gmail.com
Reviewed-By: Luigi Pinca luigipinca@gmail.com
Reviewed-By: James M Snell jasnell@gmail.com
Reviewed-By: Pranshu Srivastava rexagod@gmail.com
(cherry picked from commit da4d8de)
Checklist
make -j4 test(UNIX), orvcbuild test(Windows) passes