Unexpected behavior for execSync

[OrdinaryDude2634]

Version

20.11.0

Platform

Microsoft Windows NT 10.0.19045.0 x64

Subsystem

Child process

What steps will reproduce the bug?

execSync('net session', {windowsHide: true, stdio: ['ignore', 'ignore', 'pipe']}); should print stderr but it does not. as said in the documentation pipe is the default so changing stdio to pipe should not change anything but it stops stderr from printing, however do note it still throws the exception
this behavior is also present with ['pipe', 'pipe', 'pipe'] or any other variant

How often does it reproduce? Is there a required condition?

100% of the time. none as far as i know

What is the expected behavior? Why is that the expected behavior?

to print out stderr like it's supposed to, if you dont touch stdio it prints stderr but if you change it to pipe which is the default it dosent print stderr anymore, i do not know if it happens with stdin or stdout

What do you see instead?

nothing, explained above

Additional information

please do not forget about this:
there should be an option to not print the stderr but still keep the thrown exception detailed. if you set it to ignore it does still say "command failed" in the exception but dosent provide the information it normally provides if you set it to pipe (well in case the pipe option actually works as expected(like if you dont change stdio in the first place which is what the issue is for))
e.g.
the exception without any stdio options:

Error: Command failed: net session
System error 5 has occurred.       

Access is denied.

with ignore:

Error: Command failed: net session

PS this is my first issue so please forgive me for any issues

[avivkeller]

Have you tried adding shell: true to the options?

Also, can you reproduce in the latest version of the release line?

[OrdinaryDude2634]

i tried shell: true and i still get the same results. even if that somehow fixed the issue it should be documented or changed so it's more clear (incase shell: true actually fixed it)
also tested on 22.7.0 and still the same behavior

[avivkeller]

CC @nodejs/platform-windows @nodejs/child_process

[huseyinacacak-janea]

I tried to reproduce it locally, but saw at least one log in the terminal. It also throws an exception which you can catch and print the error message in the parent process in both cases. Do you think this should be investigated further? If so, could you provide a full example of your code that generates an error?

> cp.execSync('net session');
System error 5 has occurred.

Access is denied.

Uncaught Error: Command failed: net session
System error 5 has occurred.

Access is denied.


    at genericNodeError (node:internal/errors:984:15)
    at wrappedFn (node:internal/errors:538:14)
    at checkExecSyncError (node:child_process:891:11)
    at Object.execSync (node:child_process:963:15) 
...

> cp.execSync('net session', {stdio:'pipe'});
Uncaught Error: Command failed: net session
System error 5 has occurred.

Access is denied.


    at genericNodeError (node:internal/errors:984:15)
    at wrappedFn (node:internal/errors:538:14)
    at checkExecSyncError (node:child_process:891:11)
    at Object.execSync (node:child_process:963:15) 
...

[StefanStojanovic]

Since the last comment was unanswered for 2 months, I'll close this issue. Feel free to reopen if needed.