-
Notifications
You must be signed in to change notification settings - Fork 29.7k
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
v22.6.0 fs.cpSync crash #54476
Comments
RedYetiDev
added
the
fs
Issues and PRs related to the fs subsystem / file system.
label
Aug 21, 2024
fs.cpSync in v20.17.0 has no error. And v20.17.0 has the new feature --experimental-require-module too, it saved me, thanks. |
Likely a regression caused by #53614 - this only shows up on Windows where the native encoding is UTF16. It's possibly caused by the incorrect use of UTF8 path data #53614 (comment) |
cc @nodejs/platform-windows |
louwers
pushed a commit
to louwers/node
that referenced
this issue
Nov 2, 2024
PR-URL: nodejs#54653 Fixes: nodejs#54476 Reviewed-By: Yagiz Nizipli <yagiz@nizipli.com> Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com> Reviewed-By: Joyee Cheung <joyeec9h3@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
tpoisseau
pushed a commit
to tpoisseau/node
that referenced
this issue
Nov 21, 2024
PR-URL: nodejs#54653 Fixes: nodejs#54476 Reviewed-By: Yagiz Nizipli <yagiz@nizipli.com> Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com> Reviewed-By: Joyee Cheung <joyeec9h3@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Version
v22.6.0
Platform
Subsystem
fs
What steps will reproduce the bug?
fs.cpSync will crash if the dir contains chinese, like
fs.cpSync('C:/新建文件夹', 'C:/model', { recursive: true })
How often does it reproduce? Is there a required condition?
always
What is the expected behavior? Why is that the expected behavior?
fs.cpSync can handle the dir with chinese
What do you see instead?
no output, only crash
Additional information
No response
The text was updated successfully, but these errors were encountered: