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

S3 content missing in Browser #11100

Closed
cyberduck opened this issue Jul 6, 2020 · 3 comments
Closed

S3 content missing in Browser #11100

cyberduck opened this issue Jul 6, 2020 · 3 comments
Labels
bug s3 AWS S3 Protocol Implementation thirdparty Issue caused by third party

Comments

@cyberduck
Copy link
Collaborator

baacd44 created the issue

When I view folders of a S3 storage via the browser in Cyberduck, content is missing. If I use Go to folder and type the name of the S3 bucket followed by the folder name then I can see at least some of the content in the folder (the same folder that wasn't visible in Browser in Cyberduck). If I then type the subfolder name of one of the folders missing inside that folder then again I can see some content of the content of that folder and again need to use Go to folder to browse into the missing subfolder in that folder. Is there some limit inside Cyberduck that prevents me from using it unless I already know all the folders in S3?

@cyberduck
Copy link
Collaborator Author

@dkocher commented

We cannot reproduce the problem. Please post the transcript.

@cyberduck
Copy link
Collaborator Author

baacd44 commented

Thank you for taking the time to look into this.

Someone more experienced with Cyberduck pointed out that I should select Show Hidden Files to see these folders. For S3 storage what does Show Hidden Files mean? These folders aren't marked as deleted, are publicly accessible and are shown in the AWS S3 web view of the content. When selecting Show Hidden Files in Cyberduck, the older version of the folder is shown as of kind file with a black rectangle as an icon and the latest version is shown as of kind folder and can be expanded to see more content.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

I suspect the directory placeholder files have delete markers set.

@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 27, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug s3 AWS S3 Protocol Implementation thirdparty Issue caused by third party
Projects
None yet
Development

No branches or pull requests

1 participant