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

Jump to bottom

Synchronize Upload also downloads #5102

Closed
cyberduck opened this issue Aug 14, 2010 · 5 comments
Closed

Synchronize Upload also downloads #5102

cyberduck opened this issue Aug 14, 2010 · 5 comments
Assignees
@dkocher
Labels
bug core fixed
Milestone
3.6

Comments

@cyberduck
Copy link
Collaborator

d066db5 created the issue

I am using Cyberduck 3.5.1 (6117) to maintain a Joomla website from my laptop. I wanted to upgrade Joomla and downloaded an upgrade pack which is a tar file containing only the changed files. Then I used Cyberduck, selected the httpdocs from my website and choose Synchronize from the action menu. Then I choose the local directory containing the new file (same structure as httpdocs but a subset). In the selector that came up after Cyberduck logged in I choose Upload. I was very surprised to see later that one local directory (the directory templates that contains additional stuff on the server) had been updated in the other direction, i.e. the subdirectories on the server that were not on the laptop had been downloaded. How can this be?
@cyberduck
Copy link
Collaborator Author

d066db5 commented

I took a more detailed look and it appears that the problem is slightly less severe. It does not download files but only the directory structure. I.e. it reconstructs the directory tree on the local site but with empty directories. Still I think this is fundamentally wrong for two reasons:

  1. Upload should make NO changes to the local files. Even as in most cases empty directories are harmless there can be situations where an extra directory, though empty, has a semantic meaning.
  2. It appears that Cyberduck is also making listings of remote directories that are not present in the local tree. I guess this is the reason that it creates the local directories: to have the same structure on both sides. Anyway, I am on a slow internet connection, so it takes hours to make the remote listing, and a lot of it is useless because there is no local counterpart, if the local tree contains only a small update to the remote tree, as it is in my case. I think it should skip those remote directories that are not in the local tree.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Confirmed. Can reproduce.

@cyberduck
Copy link
Collaborator Author

4abcf1b commented

Similar problem here, using v. 3.3 (5552). Even though 'upload' is selected, it also DOWNLOADS FILES during the 'synchronize' operation.
Sorry my Version is outdated, but there is no note about that in the version history. Will confirm if 3.5 has this solved, but I guess not?!
Also, as a feature request: Upload and delete (locally) missing files would be great to maintain consistency!

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Replying to [comment:4 opfeifer]:

Similar problem here, using v. 3.3 (5552). Even though 'upload' is selected, it also DOWNLOADS FILES during the 'synchronize' operation.
Sorry my Version is outdated, but there is no note about that in the version history. Will confirm if 3.5 has this solved, but I guess not?!
Also, as a feature request: Upload and delete (locally) missing files would be great to maintain consistency!

You should upgrade. I only accept bug reports against the latest release and the issues noted in the ticket are the only synchronization issues known as of version 3.5.1.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

In d7ef94d.

@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.
Assignees

@dkocher dkocher

Labels
bug core fixed
Projects
None yet
Milestone
3.6
Development

No branches or pull requests
2 participants
@dkocher @cyberduck