-
Notifications
You must be signed in to change notification settings - Fork 772
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
fs.copy throw unexplained error ENOENT, utime #40
Comments
That's really weird. Would you
and see if you still have the same problem? Thanks! |
Trying [email protected] on 0.10.25 node. Same problem. |
Can you provide an example to help me reproduce the problem? Thanks. |
Oh, sorry. |
Need more information. |
I have the same problem. If I remove the file before coping, it works. This only happens if destiny already exists. |
same random |
@AndyOGo Please open a new issue, preferably with a reduced test case. Thanks! |
Hi
trying to copy a file from path a to another path 50% of the time, I get the following error
Error: ENOENT, utime 'my target path'
this happen right after I call fs.copy(oldPath, targetpath, function (error) { - -it get to the block with the above error - any idea ?
the file exist in the old path, but the strange thing is that it is also appeared on the target path , so the copy worked ???
what is the above error ? (what is the utime part of it) ?
I think it happens when fs.copy try to set the timestamp of the file after copying it, when I wrap it with try catch it never happened again - but the problem is that its not consistent it happen only in 50% of the times.
thanks
The text was updated successfully, but these errors were encountered: