-
Notifications
You must be signed in to change notification settings - Fork 29.6k
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
Node in terminal window gives error - Cannot read property 'setRawMode' of null #41330
Labels
tty
Issues and PRs related to the tty subsystem.
Comments
aduh95
added a commit
to aduh95/node
that referenced
this issue
Jul 12, 2022
aduh95
added a commit
to aduh95/node
that referenced
this issue
Aug 1, 2022
sidwebworks
pushed a commit
to sidwebworks/node
that referenced
this issue
Aug 26, 2022
Fixes: nodejs#41330 PR-URL: nodejs#43803 Reviewed-By: Joyee Cheung <joyeec9h3@gmail.com>
Fyko
pushed a commit
to Fyko/node
that referenced
this issue
Sep 15, 2022
Fixes: nodejs#41330 PR-URL: nodejs#43803 Reviewed-By: Joyee Cheung <joyeec9h3@gmail.com>
guangwong
pushed a commit
to noslate-project/node
that referenced
this issue
Jan 3, 2023
Fixes: nodejs/node#41330 PR-URL: nodejs/node#43803 Reviewed-By: Joyee Cheung <joyeec9h3@gmail.com>
guangwong
pushed a commit
to noslate-project/node
that referenced
this issue
Jan 3, 2023
Fixes: nodejs/node#41330 PR-URL: nodejs/node#43803 Reviewed-By: Joyee Cheung <joyeec9h3@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Version
17.3.0
Platform
Linux JPC 5.4.0-77-generic #86~18.04.1-Ubuntu SMP Fri Jun 18 01:23:22 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
Subsystem
tty
What steps will reproduce the bug?
node
process.stdin.push(null)
How often does it reproduce? Is there a required condition?
it happens every time
What is the expected behavior?
false
What do you see instead?
I see error message also
output:
Additional information
In node v0.12 & v4 it behaves like expected
In node v6, v8, v10, v12, v14, v16, v17 it gives this error
The text was updated successfully, but these errors were encountered: