-
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: remove NODE_TTY_UNSAFE_ASYNC #12057
Conversation
Nothing but trouble can ever come from it.
I'll update the original today if desired |
@Fishrock123 Do whatever makes the most sense to you, I just did this because I’d like to see it land in time for 8.0.0 |
ok so maybe I don't have enough time / interest... carry on I guess |
I don't think it makes any sense to block only on fd 0-2 though... Plus that changes the behavior in yet another way 😬 |
If anyone doesn't want to block on their own FD, they can just call the method? |
By that logic all Node.js streams should be blocking by default… these problems are about stdio, and that will cover the vast majority of all TTY streams. Also, there’s similar code in
Then we should add something for that to the public API. |
if you don't block to TTYs the same silly (esp interleaving) problems manifest. Was there any issue with it behaving as it has been? I am -1 on changing that to be async by default in some cases. |
Again, that’s true for any stream if you open it multiple times? Also, what’s special about stdio is that the API (and I’m dropping 889239b24f1237e69c5b4fdcc1f5df10586a94ec from this PR though, let’s save this discussion for something less time-constrained… |
Landed in 1b63fa1 |
Nothing but trouble can ever come from it. PR-URL: #12057 Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Colin Ihrig <[email protected]>
Rebased version of #10393 which has more or less stalled, plus addressing my own comment there.
/cc @Fishrock123 @nodejs/ctc