Repository navigation
fs.mkdir/mkdirSync recursive hang with invalid windows character #31177
Description
Activity
- addedfsIssues and PRs related to file-system APIs and the fs module.Issues and PRs related to file-system APIs and the fs module.windowsIssues and PRs related to the Windows platform.Issues and PRs related to the Windows platform.
on Jan 3, 2020 Were the @ mentions because of recursive
rmdir()(notmkdir()), or something else?@cjihrig In your case, I @-mentioned you because the linked issue (#28599) was closed by #29070, which you authored, so I thought you might have insight as to what's going on here. (I didn't look too closely at things. Sorry if the ping was a bit over-eager of me.)
Reacted by Colin Ihrig@addaleax is there any reason we can't upstream this libuv patch into Node?
@bcoe I think that libuv patch is already included in the relevant Node.js versions, so it’s probably a different (?) issue? I can try to check the next time I’m on Windows.
I'm trying to debug with visual studio (first time :D). The value of
errfor the invalid path here isUV_ENOENT. It then reaches the conditiondirname != next_path, which is true so it addsdirnameandnext_pathto the queue.
Thendirnameis handled (it exists).
Thennext_pathis handled, and we're back to the previous behavior -> infinite loopPlease review libuv/libuv#2601
Reacted by Benjamin E. Coe- added 2 commits that reference this issue
on Dec 28, 2020 - addedlibuvIssues and PRs related to the libuv dependency or the uv binding.Issues and PRs related to the libuv dependency or the uv binding.
on Dec 30, 2020 This was already fixed in libuv and released in
libuv@1.41.0.
Hi,
The following issue: #28599 doesn't seem to be resolved. I just encountered the problem on a project i work on since few days where we generate reports (some reports name has the ':' symbol in the name which is not good... i guess my collaborators are not working on Windows 😅)
Version: Node.js 13.3.0
Platform: Windows 10 - 64 Bit
How to reproduce (work with mkdirSync and mkdir promises):
mkdirSync never return. This should throw an Error.
Best Regards,
Thomas