We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
v14.17.2
Linux SRV01 4.19.66-v7+ #1253 SMP Thu Aug 15 11:49:46 BST 2019 armv7l GNU/Linux
child_process
I'll use an example where this goes wrong.
test.c
./bin the_file
child_process.execFileSync("./bin", "the_file");
So far only when I run it as a script (node app.js)
node app.js
Both output the same length.
When executed with execSync, the calculated length is always 0.
No response
The text was updated successfully, but these errors were encountered:
Where can I find test.c?
Sorry, something went wrong.
It's a clickable link. But here it is anyways: https://gist.github.com/0x2b00b1e5/367630379248098a8a6ed16226997a51
Ah, the mobile app did not underline that; Got it 👍
Have you tried using absolute paths?
child_process.execFileSync("./bin", "path/path/the_file");
No branches or pull requests
Version
v14.17.2
Platform
Linux SRV01 4.19.66-v7+ #1253 SMP Thu Aug 15 11:49:46 BST 2019 armv7l GNU/Linux
Subsystem
child_process
What steps will reproduce the bug?
I'll use an example where this goes wrong.
test.c
for your own platform./bin the_file
with your favorite shell. Observe as it prints the sizechild_process.execFileSync("./bin", "the_file");
. Observe as it prints the size.How often does it reproduce? Is there a required condition?
So far only when I run it as a script (
node app.js
)What is the expected behavior?
Both output the same length.
What do you see instead?
When executed with execSync, the calculated length is always 0.
Additional information
No response
The text was updated successfully, but these errors were encountered: