S3 empty folders nest inside themselves #8819
Comments
I should add that when I use the CLI, I create a 0-byte file of the name 'test_empty_folder'. All the folders show up correctly using the AWS management console (without any duplicate directories nested inside themselves), so it looks like things are stored 'as expected' in S3, it's just Cyberduck that's interpreting things incorrectly, even when I create the empty folder from Cyberduck itself. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
When I right-click and create an empty folder ("New Folder" option), the folder shows up twice - once nested inside itself.
I'm using 4.7 17432 on Windows 8.1.
The same thing occurs when I create an empty folder using the AWS CLI or the AWS management console - it looks like Cyberduck is incorrectly interpreting a 'test_empty_folder/' as both the directory, and the slash as another directory as the same name nested inside itself.
Attachments
empty_folder_nests_inside_itself.jpg(83.5 KiB)The text was updated successfully, but these errors were encountered: