-
Notifications
You must be signed in to change notification settings - Fork 30.1k
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: enable buffering #39253
tty: enable buffering #39253
Conversation
HWM was set to 0 which would cause e.g. stdout.write(...) to always return false. Refs: nodejs#39246
@targos not sure who's a good ping on this module? |
@nodejs/streams |
I think the highWaterMark removal from is_main_thread.js (954217a#diff-c09055446adf1d69b81595307e964da2121690a1d1bf2121845c9fcac0d86c86L152) should be reverted too. It was added years ago (bb56dcc#diff-36b7877cd8c72d2e5aa27243c142181d67d7be164927bae7503af6a720203aaeR500), and its removal can be pretty breaking. |
@addaleax this is a partial revert. Isn't it better without the semver major label and instead don't land labels or what's the thought? |
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.
@ronag Yeah, I don’t see any issues with setting the HWM for the writable side here.
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.
👍
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.
good catch
Landed in a8a8638 |
HWM was set to 0 which would cause e.g. stdout.write(...) to
always return false.
Partly reverts 954217a
Refs: #39246