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
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.
The text was updated successfully, but these errors were encountered:
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.
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.
The text was updated successfully, but these errors were encountered: