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

Synchronisation does not transfer files with equal size #3100

Closed
cyberduck opened this issue Apr 4, 2009 · 9 comments
Closed

Synchronisation does not transfer files with equal size #3100

cyberduck opened this issue Apr 4, 2009 · 9 comments

Comments

@cyberduck
Copy link
Collaborator

@cyberduck cyberduck commented Apr 4, 2009

657e742 created the issue

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:

  1. do some changes with local text file
  2. select "Synchronize..." in remote directory context menu
  3. select action "Upload"
  4. select local directory you wish to sync
  5. wait till it first synchronizes stuff as it should.
  6. Change one or few symbols local file, but make sure file size is not changed after editing
  7. In Transfers window select recent "Synchronize" task and press green "Resume" button, to re-sync local directory with remote one, and press "Continue"
  8. After task is being done, Cyberduck shows in Transfers windows fllowing information: "Transfer incomplete. 0 of 0 B".
  9. 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.


Attachments

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Apr 23, 2009

c1ecb44 commented

i'm also suffering from this bug severely!
debugging it would be most appreciated

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented May 29, 2009

a6461b6 commented

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?

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Jul 15, 2009

cwr commented

Since this behavior is documented:

http://trac.cyberduck.ch/wiki/help/en/howto/sync#FilescanbesynchronizedbyselectingthedirectorytosynchronizeinthebrowserandselectFileSynchronize.

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.

http://forums.cocoaforge.com/viewtopic.php?f=9&t=20335

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Nov 2, 2009

c87d87c commented

I can confirm that both the bug with not syncing files that are the same length and the "Transfer incomplete" bug are still in version 3.2.1.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Nov 13, 2009

@dkocher commented

Since we now support setting the timezone for a FTP bookmark and all other protocols have UTC dates, we should include a file for synchronization if the modification date is different.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Nov 13, 2009

@dkocher commented

#2523 closed as duplicate.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Dec 1, 2009

b6cb207 commented

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.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Dec 6, 2009

@dkocher commented

As or 5502bed we no more compare the file size but only the timestamp. Files with equal size are no more excluded by default.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Feb 8, 2010

e15fe2c commented

Yeah! This change is MUCH appreciated!

@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants