-
Notifications
You must be signed in to change notification settings - Fork 31k
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
can't execute /dev/stdin on linux #54200
Comments
Repro here with
Output: node:fs:441
return binding.readFileUtf8(path, stringToFlags(options.flag));
^
Error: ENOENT: no such file or directory, open '/proc/540364/fd/pipe:[14951593]'
at Object.readFileSync (node:fs:441:20)
at getMaybeCachedSource (node:internal/modules/cjs/loader:1527:18)
at Module._extensions..js (node:internal/modules/cjs/loader:1539:19)
at Module.load (node:internal/modules/cjs/loader:1282:32)
at Module._load (node:internal/modules/cjs/loader:1098:12)
at TracingChannel.traceSync (node:diagnostics_channel:315:14)
at wrapModuleLoad (node:internal/modules/cjs/loader:215:24)
at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:158:5)
at node:internal/main/run_main_module:30:49 {
errno: -2,
code: 'ENOENT',
syscall: 'open',
path: '/proc/540364/fd/pipe:[14951593]'
}
Node.js v22.5.1 |
I cannot reproduce this on MacOS m1 arch64 But I can reproduce this on Linux. Tested on |
Repro here on Windows WSL unbutu 22.04 (5.15.146.1-microsoft-standard-WSL2 #1 SMP Thu Jan 11 04:09:03 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux) printf 'console.log(1)' | node /dev/stdin
But this works fine printf 'console.log(1)' | node
|
Repro on: Output:
Working alternatives on my system:
|
I'll try to fix this. |
FWIW |
This reverts commit b998fde.
This reverts commit b998fde.
This reverts commit b998fde.
Version
v22.5.1
Platform
Subsystem
No response
What steps will reproduce the bug?
How often does it reproduce? Is there a required condition?
every time
What is the expected behavior? Why is that the expected behavior?
What do you see instead?
Additional information
related so problem https://stackoverflow.com/q/77488707/13040423
The text was updated successfully, but these errors were encountered: