Skip to content
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

Closed
nirmelamoud opened this issue Nov 21, 2013 · 8 comments
Closed

fs.copy throw unexplained error ENOENT, utime #40

nirmelamoud opened this issue Nov 21, 2013 · 8 comments

Comments

@nirmelamoud
Copy link

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

@jprichardson
Copy link
Owner

That's really weird. Would you

npm install [email protected]

and see if you still have the same problem?

Thanks!

@slonoed
Copy link

slonoed commented Apr 15, 2014

Trying [email protected] on 0.10.25 node. Same problem.

@jprichardson
Copy link
Owner

Can you provide an example to help me reproduce the problem? Thanks.

@slonoed
Copy link

slonoed commented Apr 15, 2014

Oh, sorry.
Same message, but my problem not in fs-extra.

@jprichardson
Copy link
Owner

Need more information.

@imaia
Copy link

imaia commented Mar 10, 2016

I have the same problem. If I remove the file before coping, it works. This only happens if destiny already exists.

@AndyOGo
Copy link

AndyOGo commented Mar 2, 2017

same random ENOENT errors here, though the path is correct. Really weird.
Happened as I switched from sync to async APIs.

@RyanZim
Copy link
Collaborator

RyanZim commented Mar 2, 2017

@AndyOGo Please open a new issue, preferably with a reduced test case. Thanks!

Repository owner locked and limited conversation to collaborators Mar 2, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants