doc: child_process: clarify subprocess.pid can be undefined when ENOENT

[dr-js]

From the code nodejs@8 and up should behave the same: https://github.com/nodejs/node/blame/v8.17.0/lib/internal/child_process.js#L290-L316

And a short test snippet:

const{ spawn }=require('child_process')constsubProcess=spawn('non-exist-command')subProcess.on('error',(error)=>console.warn('mute Unhandled "error" event:',error))console.log('- pid:',subProcess.pid)process.nextTick(()=>console.log('- after error emit'))console.log('== end of test ==')

[aduh95]

Do you want to update the test to make sure there's no regression in the future?

node/test/parallel/test-child-process-spawn-error.js

Lines 29 to 42 in 3df5afb

	constenoentPath='foo123';
	constspawnargs=['bar'];
	assert.strictEqual(fs.existsSync(enoentPath),false);
	constenoentChild=spawn(enoentPath,spawnargs);
	// Verify that stdio is setup if the error is not EMFILE or ENFILE.
	assert.notStrictEqual(enoentChild.stdin,undefined);
	assert.notStrictEqual(enoentChild.stdout,undefined);
	assert.notStrictEqual(enoentChild.stderr,undefined);
	assert(Array.isArray(enoentChild.stdio));
	assert.strictEqual(enoentChild.stdio[0],enoentChild.stdin);
	assert.strictEqual(enoentChild.stdio[1],enoentChild.stdout);
	assert.strictEqual(enoentChild.stdio[2],enoentChild.stderr);

[dr-js]

Sure, I'll try update the test.

[dr-js]

@aduh95 Upon adding the test, I found the pid value is a bit more complex than I thought:

• an async spawn with invalid cwd will get pid undefined (expected)
• an async spawn with invalid commad and shell: false will get pid undefined (expected)
• an async spawn with invalid commad and shell: true will get pid of the shell (expected)
• a sync spawn seems always return pid (strange)

Should I add more detailed behavior description to the doc and update test for async and sync spawn,
or keep it undocumented behavior as it's not so straightforward for now?

The test code for this:

[test.js]

[()=>testSpawn('with invalid command',['non-exist-command']),()=>testSpawn('with invalid command and `shell: true`',['non-exist-command',{shell: true}]),()=>testSpawn('with invalid cwd',['node',{cwd: './non/exist/cwd/path/'}]),()=>testSpawn('invalid cwd and `shell: true`',['node',{cwd: './non/exist/cwd/path/',shell: true}]),()=>testSpawnSync('with invalid command',['non-exist-command']),()=>testSpawnSync('with invalid command and `shell: true`',['non-exist-command',{shell: true}]),()=>testSpawnSync('with invalid cwd',['node',{cwd: './non/exist/cwd/path/'}]),()=>testSpawnSync('invalid cwd and `shell: true`',['node',{cwd: './non/exist/cwd/path/',shell: true}])].forEach((testFunc,index)=>setTimeout(testFunc,index*200))constformatError=(error)=>error&&error.message// const formatError = (error) => error && error.stack // for more detailconsttestSpawn=(title='',spawnArgs='')=>{console.log(`\n== test spawn ${title} ==`)const{ spawn }=require('child_process')constsubProcess=spawn(...spawnArgs)subProcess.on('error',(error)=>console.warn('- "error" event:',formatError(error)))// mute Unhandled "error" event or the test will exitconsole.log('- pid:',subProcess.pid,'exitCode:',subProcess.exitCode)process.nextTick(()=>console.log('- nextTick pid:',subProcess.pid,'exitCode:',subProcess.exitCode))setTimeout(()=>console.log('- after 100ms pid:',subProcess.pid,'exitCode:',subProcess.exitCode),100)}consttestSpawnSync=(title='',spawnArgs='')=>{console.log(`\n== test spawnSync ${title} ==`)const{ spawnSync }=require('child_process')constoutcome=spawnSync(...spawnArgs)// NOTE: not a `subProcess`console.log('- pid:',outcome.pid,'status',outcome.status)console.log('- error',formatError(outcome.error))}

And the output:

[v15.6.0 linux x64]

v15.6.0 linux x64
== test spawn with invalid command ==
- pid: undefined exitCode: null
- "error" event: spawn non-exist-command ENOENT
- nextTick pid: undefined exitCode: -2
- after 100ms pid: undefined exitCode: -2
== test spawn with invalid command and `shell: true` ==
- pid: 30493 exitCode: null
- nextTick pid: 30493 exitCode: null
- after 100ms pid: 30493 exitCode: 127
== test spawn with invalid cwd ==
- pid: undefined exitCode: null
- "error" event: spawn node ENOENT
- nextTick pid: undefined exitCode: -2
- after 100ms pid: undefined exitCode: -2
== test spawn invalid cwd and `shell: true` ==
- pid: undefined exitCode: null
- "error" event: spawn /bin/sh ENOENT
- nextTick pid: undefined exitCode: -2
- after 100ms pid: undefined exitCode: -2
== test spawnSync with invalid command ==
- pid: 30496 status null
- error spawnSync non-exist-command ENOENT
== test spawnSync with invalid command and `shell: true` ==
- pid: 30497 status 127
- error undefined
== test spawnSync with invalid cwd ==
- pid: 30498 status null
- error spawnSync node ENOENT
== test spawnSync invalid cwd and `shell: true` ==
- pid: 30499 status null
- error spawnSync /bin/sh ENOENT

[v15.6.0 win32 x64]

v15.6.0 win32 x64
== test spawn with invalid command ==
- pid: undefined exitCode: null
- "error" event: spawn non-exist-command ENOENT
- nextTick pid: undefined exitCode: -4058
- after 100ms pid: undefined exitCode: -4058
== test spawn with invalid command and `shell: true` ==
- pid: 21860 exitCode: null
- nextTick pid: 21860 exitCode: null
- after 100ms pid: 21860 exitCode: 1
== test spawn with invalid cwd ==
- pid: undefined exitCode: null
- "error" event: spawn node ENOENT
- nextTick pid: undefined exitCode: -4058
- after 100ms pid: undefined exitCode: -4058
== test spawn invalid cwd and `shell: true` ==
- pid: undefined exitCode: null
- "error" event: spawn C:\Windows\system32\cmd.exe ENOENT
- nextTick pid: undefined exitCode: -4058
- after 100ms pid: undefined exitCode: -4058
== test spawnSync with invalid command ==
- pid: 0 status null
- error spawnSync non-exist-command ENOENT
== test spawnSync with invalid command and `shell: true` ==
- pid: 8864 status 1
- error undefined
== test spawnSync with invalid cwd ==
- pid: 0 status null
- error spawnSync node ENOENT
== test spawnSync invalid cwd and `shell: true` ==
- pid: 0 status null
- error spawnSync C:\Windows\system32\cmd.exe ENOENT

[aduh95]

Hum that's weird indeed, that might be a bug with spawnSync implementation. The "good news" is that the part of the docs you are modifying only covers the async version, the "bad news" is we now have to investigate for the pid in sync calls. Do you want to open an issue for the PID, and we can add a test in test/known_issues?

[dr-js]

@aduh95 Sure, so in this PR I'll add docs & test checks for subProcess.pid, as it's only from the async version of spawn.

And I'll open another Issue with above test to discuss sync spawn pid behavior, and maybe a PR to add test to test/known_issues.

[Trott]

LGTM with doc updates. @nodejs/documentation @nodejs/child_process

[nodejs-github-bot]

CI: https://ci.nodejs.org/job/node-test-pull-request/36242/

[aduh95]

Landed in 574590d...1e0cfa3