-
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
doc: several properties undocumented on child process #27206
Comments
Its probably the pair of |
Add documentation for subprocess.exitCode, subprocess.signalCode, subprocess.spawnargs, and subprocess.spawnfile. PR-URL: #31342 Fixes: #27206 Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: Rich Trott <[email protected]>
Add documentation for subprocess.exitCode, subprocess.signalCode, subprocess.spawnargs, and subprocess.spawnfile. PR-URL: #31342 Fixes: #27206 Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: Rich Trott <[email protected]>
Add documentation for subprocess.exitCode, subprocess.signalCode, subprocess.spawnargs, and subprocess.spawnfile. PR-URL: #31342 Fixes: #27206 Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: Rich Trott <[email protected]>
Tracking back as far as Node 0.12 it seems that the documentation for
ChildProcess
is missing several properties.exitCode
- if the process exited will contain the exit code, elsenull
. Useful in combination withkilled
→if (proc.exitCode !== null || proc.killed)
to see if the process is still running.signalCode
- not sure what that is good for.spawnfile
&spawnargs
the initial properties of the spawning. In combination with exec will show what shell is used. Useful for debugging.The text was updated successfully, but these errors were encountered: