-
Notifications
You must be signed in to change notification settings - Fork 30.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
tty: fix TypeError when stream is closed #43803
Conversation
5697cf3
to
9e6812f
Compare
/cc @nodejs/tty |
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.
Is it useful to handle this gracefully? I would rather see an error that the stream is already destroyed? Otherwise it's difficult to know what happens as a user.
@BridgeAR see the linked issue, and I have also been annoyed by that error in other occasions. I struggled to find a good way to reproduce the error reliably, and I agree that the test as-is doesn't feel like something we would necessarily want to support, but the issue is real, and it looks like to me that fixing it is less problematic than not fixing it. |
Landed in ab89024 |
Fixes: nodejs#41330 PR-URL: nodejs#43803 Reviewed-By: Joyee Cheung <joyeec9h3@gmail.com>
Fixes: nodejs#41330 PR-URL: nodejs#43803 Reviewed-By: Joyee Cheung <joyeec9h3@gmail.com>
Fixes: nodejs/node#41330 PR-URL: nodejs/node#43803 Reviewed-By: Joyee Cheung <joyeec9h3@gmail.com>
Fixes: nodejs/node#41330 PR-URL: nodejs/node#43803 Reviewed-By: Joyee Cheung <joyeec9h3@gmail.com>
Alternative to #41335 that got stalled.
Fixes: #41330