-
-
Notifications
You must be signed in to change notification settings - Fork 150
should rename account for 'EBUSY' on Windows? #127
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
Comments
conceptualspace
added a commit
to konode001/node-graceful-fs
that referenced
this issue
May 2, 2018
when rename fails with EBUSY we should also retry like we do with EPERM and EACCESS behaviour is consistent with rm (https://github.com/isaacs/rimraf) resolves isaacs#127
Open
Unlink |
We're having this issue in pnpm now, where we use graceful-fs |
This should be fixed now. |
zkochan
added a commit
to zoli-forks/node-graceful-fs
that referenced
this issue
Apr 4, 2023
Recently a similar fix was merged for rename isaacs#127. But a similar issue happens on copy as well. ref pnpm/pnpm#6201
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
along with EACCESS and EPERM errors, EBUSY can bubble up if a file is temporarily locked in windows (for example during AV scan or Dropbox sync).
rimraf treats them the same, shouldnt graceful-fs as well?
The text was updated successfully, but these errors were encountered: