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

Crash when S3 object has dot in key #2575

Closed
cyberduck opened this issue Sep 13, 2008 · 3 comments
Closed

Crash when S3 object has dot in key #2575

cyberduck opened this issue Sep 13, 2008 · 3 comments
Assignees
Labels
bug fixed s3 AWS S3 Protocol Implementation
Milestone

Comments

@cyberduck
Copy link
Collaborator

6bcf6c2 created the issue

I have an object in my S3 bucket with the key:

jra/prc_20070813/nodrm/rc1/./uploadNoDRM_Solaris.rb.wmv

Cyber duck hangs (infinite loop?) attempting to expand this virtual path in the directory tree view.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

How did you manage to create a file with that key? All clients I know of won't allow this as . is usually a reserved character denoting the current directory.

To track down this bug, can you please post some logging information. Set the logging level in Cyberduck to debug by pasting

defaults write ch.sudo.cyberduck logging DEBUG

into a Terminal.app window and restarting Cyberduck. Can you then post the console.log from Applications/Utilities/Console.app here. Thanks.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Resolution is delayed as I cannot find a tool which allows me to create a dot file on S3 that would allow me to reproduce the issue.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

This should be resolved by the fix for #3347.

@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.
Labels
bug fixed s3 AWS S3 Protocol Implementation
Projects
None yet
Development

No branches or pull requests

2 participants