Cyberduck Mountain Duck CLI

#265 closed defect (fixed)

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

Reported by: Owned by: dkocher
Priority: normal Milestone: 2.6
Component: core Version: 2.5.5
Severity: major Keywords:
Cc: Architecture:


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 :-(


Change History (2)

comment:1 Changed on Mar 25, 2006 at 10:35:29 PM by dkocher

  • Milestone set to 2.5.6
  • Severity changed from normal to major
  • Status changed from new to assigned

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.

comment:2 Changed on May 15, 2006 at 10:03:57 AM by dkocher

  • Resolution set to fixed
  • Status changed from assigned to closed
Note: See TracTickets for help on using tickets.