-
Notifications
You must be signed in to change notification settings - Fork 29.8k
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
http2: simplify timeout tracking #19206
Conversation
There’s no need to reset the chunk counter for every write.
@addaleax would you be so kind and check the CI? I have the feeling there might be related errors, e.g., https://ci.nodejs.org/job/node-test-commit-linux-containered/2768/nodes=ubuntu1604_sharedlibs_openssl110_x64/console. |
@BridgeAR Thanks for checking! I don’t think the errors are related, because this only affects http2, whereas the test only uses the built-in But still, let’s start a new CI just to be sure: https://ci.nodejs.org/job/node-test-commit/16842/ |
Landed in 90e70b8 |
There’s no need to reset the chunk counter for every write. PR-URL: #19206 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Daniel Bevenius <daniel.bevenius@gmail.com> Reviewed-By: Anatoli Papirovski <apapirovski@mac.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
There’s no need to reset the chunk counter for every write. PR-URL: #19206 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Daniel Bevenius <daniel.bevenius@gmail.com> Reviewed-By: Anatoli Papirovski <apapirovski@mac.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
There’s no need to reset the chunk counter for every write. PR-URL: #19206 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Daniel Bevenius <daniel.bevenius@gmail.com> Reviewed-By: Anatoli Papirovski <apapirovski@mac.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
There’s no need to reset the chunk counter for every write. PR-URL: nodejs#19206 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Daniel Bevenius <daniel.bevenius@gmail.com> Reviewed-By: Anatoli Papirovski <apapirovski@mac.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
I can open a PR first thing tomorrow -- how did you find out that this commit wasn't backported? I'm wondering if there are others that slipped through the crack as well, somehow. |
There’s no need to reset the chunk counter for every write. PR-URL: nodejs#19206 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Daniel Bevenius <daniel.bevenius@gmail.com> Reviewed-By: Anatoli Papirovski <apapirovski@mac.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
@kjin Maybe the issue is that this wasn’t labeled |
@kjin As far as PRs that were labeled
|
There’s no need to reset the chunk counter for every write. Backport-PR-URL: #23774 PR-URL: #19206 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Daniel Bevenius <daniel.bevenius@gmail.com> Reviewed-By: Anatoli Papirovski <apapirovski@mac.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Splitting out from #18936:
There’s no need to reset the chunk counter for every write.
Checklist
make -j4 test
(UNIX), orvcbuild test
(Windows) passes