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
When moving a directory A into a directory B which already has a subdirectory named A, Cyberduck prompts whether I want to overwrite the subdirectory and if I confirm, it errors saying it cannot delete directory A: https://i.imgur.com/jCeSykk.mp4
This error is independent on whether there are files in the directory or not. It also does not seem to be a permission error, because trying to perform a deletion through Cyberduck works fine.
The behavior I'd expect is that Cyberduck attempts to merge the two directories instead, and only asks for overwriting specifically for colliding files. It's unclear what exactly Cyberduck is attempting to do instead right now, but in the end no action is taken and it only shows the above error.
The text was updated successfully, but these errors were encountered:
I can't reproduce the issue within the latest Snapshot Build of Cyberduck. Do you still see this issue within the latest Snapshot Build (8.0.0 (36198))?
I just tested it on the current latest snapshot build (8.0.1 (36247)) and I still see this issue. However, unlike in my initial report, it no longer errors if the two directories are empty. But when there are files in the directories, it fails with the same error.
When moving a directory A into a directory B which already has a subdirectory named A, Cyberduck prompts whether I want to overwrite the subdirectory and if I confirm, it errors saying it cannot delete directory A: https://i.imgur.com/jCeSykk.mp4
This error is independent on whether there are files in the directory or not. It also does not seem to be a permission error, because trying to perform a deletion through Cyberduck works fine.
The behavior I'd expect is that Cyberduck attempts to merge the two directories instead, and only asks for overwriting specifically for colliding files. It's unclear what exactly Cyberduck is attempting to do instead right now, but in the end no action is taken and it only shows the above error.
The text was updated successfully, but these errors were encountered: