Uh oh!
There was an error while loading. Please reload this page.
tty: remove NODE_TTY_UNSAFE_ASYNC - #12057
Conversation
Nothing but trouble can ever come from it.
addaleax
commented
Mar 27, 2017
Fishrock123
commented
Mar 27, 2017
I'll update the original today if desired |
addaleax
commented
Mar 27, 2017
@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 |
Fishrock123
commented
Mar 29, 2017
ok so maybe I don't have enough time / interest... carry on I guess |
Fishrock123
commented
Mar 29, 2017
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 😬 |
Fishrock123
commented
Mar 29, 2017
If anyone doesn't want to block on their own FD, they can just call the method? |
addaleax
commented
Mar 29, 2017
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. |
addaleax
commented
Mar 29, 2017
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… |
addaleax
commented
Mar 31, 2017
Landed in 1b63fa1 |
Nothing but trouble can ever come from it. PR-URL: #12057 Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Rebased version of #10393 which has more or less stalled, plus addressing my own comment there.
/cc @Fishrock123 @nodejs/ctc