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

Repeating a sync after previous one failed due to a disconnect can delete file contents. #12213

Closed
cyberduck opened this issue Mar 9, 2006 · 1 comment

Comments

@cyberduck
Copy link
Collaborator

@cyberduck cyberduck commented Mar 9, 2006

addf5fc created the issue

I synced three text files from my Mac to unix host. The unix server timed out after the
second file copied but before the third one completed, resulting in a zero lenth copy
of the file being left on the server. Guess what happend when I tried re-syncing?
Yep, I missed the fact that the change in the direction of the upload/download arrow
and wrote that zero byte file over the original one on my Mac.

Call pilot error if you want. Call it a feature. But it's really really nasty and I've just
lost shed load of work because of it. Maybe it would be a good idea to remember if
the last sync failed and not reverse the sense of the copy without confirmation.

Sorry, but I'm going back to raw scp :-(

/S.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Mar 25, 2006

@dkocher commented

The fix will be to never treat zero-length file as newer files. However you do see in the confirmation dialog which file will get replaced and can exclude files.

Loading

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants