Repository navigation
node.js responds nothing and even no error when executing *.js file which be stored in specific path with Non-ASCII characters since v22.5.0 #55773
Description
Activity
- changed the title
[-]node.js responds nothing and even no error when executing *.js file be stored in special path with Non-ASCII characters since v22.5.0[/-][+]node.js responds nothing and even no error when executing *.js file which be stored in specific path with Non-ASCII characters since v22.5.0[/+]on Nov 8, 2024 Can you set
NODE_DEBUG=*in your env and re-run it please? Also, please consider copying/pasting rather than sharing screenshots – screenshots can make things harder for folks using screen-readers, folks using a low-bandwidth internet, and makes it needlessly harder to copy/paste the output if I want to search through the codebase.Can you set
NODE_DEBUG=*in your env and re-run it please? Also, please consider copying/pasting rather than sharing screenshots – screenshots can make things harder for folks using screen-readers, folks using a low-bandwidth internet, and makes it needlessly harder to copy/paste the output if I want to search through the codebase.Thanks for your reply, but I have to clarify that the screenshots is only for a intuitive display, the commands and step to reproduce the issue are all declared above.
And I have re-installed the Node.JS with version
v22.5.0, setNODE_DEBUG=*and return the script, but nothing changed:D:\>node -v v22.5.0 D:\>mkdir "D:\2024年11月" D:\>echo console.log(123);>"D:\2024年11月\test.js" D:\>type "D:\2024年11月\test.js" console.log(123); D:\>set NODE_DEBUG=* D:\>echo %NODE_DEBUG% * D:\>node "D:\2024年11月\test.js" D:\> D:\>mkdir "D:\2024▲11▲" D:\>echo console.log(123);>"D:\2024▲11▲\test.js" D:\>type "D:\2024▲11▲\test.js" console.log(123); D:\>set NODE_DEBUG=* D:\>echo %NODE_DEBUG% * D:\>node "D:\2024▲11▲\test.js" D:\>I really think it's stable and easy to reproduce...
FWIW I cannot reproduce on macOS on
main.$ mkdir '2024年11月' $ echo 'console.log(123)' > '2024年11月/index.js' $ ./node '2024年11月' 123
I have to clarify that the screenshots is only for a intuitive display
Sure, hopefully you'll agree that the text version does as good as a job at that, without the shortcoming of a screenshot :)
FWIW I cannot reproduce on macOS on
main.$ mkdir '2024年11月' $ echo 'console.log(123)' > '2024年11月/index.js' $ ./node '2024年11月' 123I have to clarify that the screenshots is only for a intuitive display
Sure, hopefully you'll agree that the text version does as good as a job at that, without the shortcoming of a screenshot :)
Ok, since this could not be reproduced in all environments, I would close this issue and do some more test in other envionment like WSL or remote Linux server before I submit again, thanks for your test, have a nice day 😃
We can also leave it open and see if someone with a Windows machine can reproduce (assuming it's Windows-related)
I wasn't able to reproduce this issue with v22.5.0, v22.10.0, and v23.1.0 on Windows.
I was able to reproduce this issue on my environment, so I will work on this.
Version
v22.5.0
Platform
Subsystem
No response
What steps will reproduce the bug?
mkdir "D:\2024年11月"echo console.log(123);>"D:\2024年11月\test.js"node "D:\2024年11月\test.js"How often does it reproduce? Is there a required condition?
It always happend as long as the path of script file is certain.
What is the expected behavior? Why is that the expected behavior?
The script file was completely launched and executed, print
123in stdout or some other error in stderr.What do you see instead?
No any response from node.exe, can not figure out what happened, and you will got a
read ECONNRESETerror if you run command to inspect likenode inspect "D:\2024年11月\test.js"Additional information