Skip to content
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

stream: don't deadlock on aborted stream #29376

Closed
wants to merge 4 commits into from

Conversation

ronag
Copy link
Member

@ronag ronag commented Aug 30, 2019

Not all streams (e.g. http.ClientRequest) will always emit 'close' after 'aborted'.

Noticed this while fixing some stuff in fastify. I think the root issue will be fixed by #27984. But I still think it's a good idea to have this fix/workaround in the npm stream-readable package for older node versions.

Checklist
  • make -j4 test (UNIX), or vcbuild test (Windows) passes
  • tests and/or benchmarks are included
  • documentation is changed or added
  • commit message follows commit guidelines

Not all streams (e.g. http.ClientRequest) will always emit
'close' after 'aborted'.
@ronag
Copy link
Member Author

ronag commented Aug 30, 2019

ping @mcollina

Copy link
Member

@mcollina mcollina left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@nodejs-github-bot
Copy link
Collaborator

@nodejs-github-bot
Copy link
Collaborator

@mcollina
Copy link
Member

mcollina commented Sep 2, 2019

Landed in 897587c

@mcollina mcollina closed this Sep 2, 2019
mcollina pushed a commit that referenced this pull request Sep 2, 2019
Not all streams (e.g. http.ClientRequest) will always emit
'close' after 'aborted'.

PR-URL: #29376
Reviewed-By: Matteo Collina <matteo.collina@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
BridgeAR pushed a commit that referenced this pull request Sep 3, 2019
Not all streams (e.g. http.ClientRequest) will always emit
'close' after 'aborted'.

PR-URL: #29376
Reviewed-By: Matteo Collina <matteo.collina@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
@BridgeAR BridgeAR mentioned this pull request Sep 3, 2019
BridgeAR pushed a commit that referenced this pull request Sep 4, 2019
Not all streams (e.g. http.ClientRequest) will always emit
'close' after 'aborted'.

PR-URL: #29376
Reviewed-By: Matteo Collina <matteo.collina@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants