-
Notifications
You must be signed in to change notification settings - Fork 12
"Impossible:" errors whenever a command to be run doesn't exist #65
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
Comments
Hi-Angel
added a commit
to Hi-Angel/purescript-node-child-process
that referenced
this issue
Mar 21, 2025
When a non-existing command is attempted to run, both status and signal will be null, which leads to ChildProcess module crashing. Obviously, this is incorrect behavior. The problem is more general than that though: any system error that would result in failing to run a process would result in the module crash. Fix that by checking for such case. Fixes: purescript-node#65
4 tasks
Hi-Angel
added a commit
to Hi-Angel/purescript-node-child-process
that referenced
this issue
Mar 21, 2025
When a non-existing command is attempted to run, both status and signal will be null, which leads to ChildProcess module crashing. Obviously, this is incorrect behavior. The problem is more general than that though: any system error that would result in failing to run a process would result in the module crash. Fix that by checking for such case. Fixes: purescript-node#65
Hi-Angel
added a commit
to Hi-Angel/purescript-node-child-process
that referenced
this issue
Mar 21, 2025
When a non-existing command is attempted to run, both status and signal will be null, which leads to ChildProcess module crashing. Obviously, this is incorrect behavior. The problem is more general than that though: any system error that would result in failing to run a process would result in the module crash. Fix that by checking for such case. Fixes: purescript-node#65
Sent a PR to fix that. |
Hi-Angel
added a commit
to Hi-Angel/purescript-node-child-process
that referenced
this issue
Mar 21, 2025
When a non-existing command is attempted to run, both status and signal will be null, which leads to ChildProcess module crashing. Obviously, this is incorrect behavior. The problem is more general than that though: any system error that would result in failing to run a process would result in the module crash. Fix that by checking for such case. Fixes: purescript-node#65
Hi-Angel
added a commit
to Hi-Angel/purescript-node-child-process
that referenced
this issue
Mar 21, 2025
When a non-existing command is attempted to run, both status and signal will be null, which leads to ChildProcess module crashing. Obviously, this is incorrect behavior. The problem is more general than that though: any system error that would result in failing to run a process would result in the module crash. Fix that by checking for such case. Fixes: purescript-node#65
Hi-Angel
added a commit
to Hi-Angel/purescript-node-child-process
that referenced
this issue
Mar 22, 2025
When a non-existing command is attempted to run, both status and signal will be null, which leads to ChildProcess module crashing. Obviously, this is incorrect behavior. The problem is more general than that though: any system error that would result in failing to run a process would result in the module crash. Fix that by checking for such case. Fixes: purescript-node#65
Hi-Angel
added a commit
to Hi-Angel/purescript-node-child-process
that referenced
this issue
Mar 22, 2025
When a non-existing command is attempted to run, both status and signal will be null, which leads to ChildProcess module crashing. Obviously, this is incorrect behavior. The problem is more general than that though: any system error that would result in failing to run a process would result in the module crash. Fix that by checking for such case. Fixes: purescript-node#65
Hi-Angel
added a commit
to Hi-Angel/purescript-node-child-process
that referenced
this issue
Mar 22, 2025
When a non-existing command is attempted to run, both status and signal will be null, which leads to ChildProcess module crashing. Obviously, this is incorrect behavior. The problem is more general than that though: any system error that would result in failing to run a process would result in the module crash. Fix that by checking for such case. Fixes: purescript-node#65
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
In practice I see quite often an error:
Looks quite possible… Further digging shows that this is due
ChildProcess
logic not accounting for bothstatus
andsignal
to benull
for valid reasons (which may also be some system error, not just "command not found").Steps to reproduce
Execute this code:
Expected
Actual
A crash with
Impossible:
spawnSync
child process neither exited nor was killed.The text was updated successfully, but these errors were encountered: