You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When attempting to rename/move a parent folder that contains subfolders on Windows, the operation often fails with an EPERM (Error: Permission Denied) error. This issue arises due to Windows’ strict permissions, file locking, and background processes keeping file handles open. Applications such as Visual Studio Code also face this issue when using the Node.js fs.promises.rename function, as documented in the following issues:
This behavior disrupts the user experience, making it difficult to consistently rename folders that contain subfolders, especially when some files are in use by the system or other processes.
Mockups or Images of the feature
20241001-0947-49.3882630.mp4
The text was updated successfully, but these errors were encountered:
Pragadesh-45
changed the title
Improve Folder Renaming Handling to Address EPERM Errors
Improve Folder Renaming/Move Handling to Address EPERM Errors
Oct 1, 2024
Pragadesh-45
changed the title
Improve Folder Renaming/Move Handling to Address EPERM Errors
Improve Folder Rename/Move Handling to Address EPERM Errors
Oct 1, 2024
I have checked the following:
Describe the feature you want to add:
Existing issues: #678
Problem:
When attempting to rename/move a parent folder that contains subfolders on Windows, the operation often fails with an
EPERM
(Error: Permission Denied) error. This issue arises due to Windows’ strict permissions, file locking, and background processes keeping file handles open. Applications such as Visual Studio Code also face this issue when using the Node.jsfs.promises.rename
function, as documented in the following issues:This behavior disrupts the user experience, making it difficult to consistently rename folders that contain subfolders, especially when some files are in use by the system or other processes.
Mockups or Images of the feature
20241001-0947-49.3882630.mp4
The text was updated successfully, but these errors were encountered: