I often have to synchronize local directory with ftp-server directory, and seems like Cyberduck doesn't handle this task as supposed to - it doesn't sync files, whose size in bytes has not been changed. Even if I change half of the file and size is remain the same - file is NOT being sync-d.
Steps to reproduce the problem:
do some changes with local text file
select "Synchronize..." in remote directory context menu
select action "Upload"
select local directory you wish to sync
wait till it first synchronizes stuff as it should.
Change one or few symbols local file, but make sure file size is not changed after editing
In Transfers window select recent "Synchronize" task and press green "Resume" button, to re-sync local directory with remote one, and press "Continue"
After task is being done, Cyberduck shows in Transfers windows fllowing information: "Transfer incomplete. 0 of 0 B".
As a result, local file has NOT being synchronized, though file has been changed.
Also, another bug is detected with this issue: after synchronization, either successful or not, Cyberduck shows message "Transfer incomplete", even if all files are sync-d successfully.
I just uploaded a snapshot of this error, showing two files of the same size but with different time stamps. Synchronize does not identify them as different. Thank goodness I remembered changing the file today. Worse, the file size, while the same, is not that reported by Cyberduck (28.5KB). The files are actually 32KB (29,184 Bytes). There are actual differences in these two Excel files.
I am using Cyberduck Version 3.2 (4648) on my Intel MacBook running OS X, ver 10.5.6. I agree that this is extremely serious. If I want to go back to an earlier version of Cyberbuck, when did this error first creep in?
it is unclear if the author considers this a bug or a feature. I vote for "bug". I frequently want to synchronize files whose length have not changed. As a result I end up having to do the sync multiple times, going back and making a gratuitous change in length just to get sync to work.
I like the way WinSCP handles this (I often work on a windows machine at work). Because it is very difficult to compare files without downloading them all, WinSCP first does a thorough synchronization by downloading all files to the local directory (warning when modification dates are newer on the local side of course). From then, you can make it look for changes on the local files, and the changed files are uploaded automatically, thus automatically keeping the remote directory in sync.
All I have to do there is turning on the synchronization function and edit my files.