-
-
Notifications
You must be signed in to change notification settings - Fork 31.4k
http2 compat does not emit 'timeout' event on request object #20079
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Labels
Comments
Yeah, this is definitely incorrect. We don't emit it on the response either. Both need to be fixed and should match the logic in |
DaAitch
added a commit
to wildoak/node
that referenced
this issue
May 23, 2018
A timeout in a http2 stream should emit a 'timeout' event also on request and response object. If there is no listener on stream, request or response, stream should immediately be destroyed. Fixes: nodejs#20079
4 tasks
3 tasks
jasnell
added a commit
to jasnell/node
that referenced
this issue
Aug 10, 2018
kjin
pushed a commit
to kjin/node
that referenced
this issue
Oct 3, 2018
Fixes: nodejs#20079 PR-URL: nodejs#22252 Reviewed-By: Matteo Collina <matteo.collina@gmail.com> Reviewed-By: Trivikram Kamat <trivikr.dev@gmail.com>
kjin
pushed a commit
to kjin/node
that referenced
this issue
Oct 16, 2018
v8.x Backport Note: The timeout has been increased to 10ms. Fixes: nodejs#20079 PR-URL: nodejs#22252 Reviewed-By: Matteo Collina <matteo.collina@gmail.com> Reviewed-By: Trivikram Kamat <trivikr.dev@gmail.com>
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
Labels
http2 compat does not emit 'timeout' event on request object. It only invokes the
setTimeout
callback argument.The text was updated successfully, but these errors were encountered: