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

Copy & Paste copying wrong files #6659

Closed
cyberduck opened this issue Apr 28, 2012 · 1 comment
Closed

Copy & Paste copying wrong files #6659

cyberduck opened this issue Apr 28, 2012 · 1 comment

Comments

@cyberduck
Copy link
Collaborator

@cyberduck cyberduck commented Apr 28, 2012

96fa9f9 created the issue

This is just a heads-up to what is a critical bug regarding incorrect copy/paste behavior. When I paste to a selected directory, CyberDuck copies from the wrong location.
In our case we have multiple s3 buckets with sometimes 1000s of keys so I can see a buggy copy/paste displayed in the progress line as hundreds of files being copied. I have to disconnect to stop the copying and I then I find a directory full of files that I didn't intend to copy.

I wish I had more specific description of the problem, but I have observed the behavior several times using CyberDuck and my colleague also observed the same behavior. Even though I don't have the exact details to reproduce it, the problem seems so severe that I wanted to give you a notice. My colleague and I suspect that there is an internal data structure of cached s3 keys and that the paste operation is accidentally referencing the wrong data.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Nov 26, 2012

@dkocher commented

I cannot reproduce this issue with the latest snapshot build available.

@cyberduck cyberduck closed this Nov 26, 2012
@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
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants