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

Directories still showing when delete marker present #10484

Closed
cyberduck opened this issue Oct 3, 2018 · 6 comments
Closed

Directories still showing when delete marker present #10484

cyberduck opened this issue Oct 3, 2018 · 6 comments
Assignees
Labels
bug s3 AWS S3 Protocol Implementation worksforme
Milestone

Comments

@cyberduck
Copy link
Collaborator

cyberduck commented Oct 3, 2018

70d6bb8 created the issue

Even with "show hidden files" turned off, when the contents of a folder are deleted where each object is listed along with it's delete marker, the folder heirachy above shows in the client like it's still present.

Surely by turning off "show hidden files", these empty (delete marked) folders should not show up?

@cyberduck
Copy link
Collaborator Author

cyberduck commented Oct 4, 2018

@dkocher commented

Are you referring to versioned objects in S3?

@cyberduck
Copy link
Collaborator Author

cyberduck commented Oct 5, 2018

70d6bb8 commented

Yes, after some further research it's related to versioning.

So within a bucket, if I create a folder (at least what looks like a folder anyway), and populate it with files. With versioning turned on, I then delete those files and the containing folder. They all get versioned and have a "delete marker" present.

If I then disable "show hidden files", the contained files will disappear, but the folders are still visible. If I enable "show hidden files", then both folders and files are visible.

Surely the behavior should be that the folders are also not visible when you disable "show hidden files"? After all, they've been deleted, versioned and have "delete marker" present also?

@cyberduck
Copy link
Collaborator Author

cyberduck commented Jan 16, 2019

@dkocher commented

Ticket retargeted after milestone closed

@cyberduck
Copy link
Collaborator Author

cyberduck commented Feb 26, 2019

@ylangisc commented

Can you please check and report back if the issue still persists in the latest version as we have changed the handling of versioned objects?

@cyberduck
Copy link
Collaborator Author

cyberduck commented Feb 26, 2019

70d6bb8 commented

Sure, which version do you want me to test. Currently I have 6.9.3 (30061).

@cyberduck
Copy link
Collaborator Author

cyberduck commented Feb 26, 2019

@dkocher commented

Replying to [comment:8 cpharvey]:

Sure, which version do you want me to test. Currently I have 6.9.3 (30061).
Can you confirm you still see the issue with this version.

@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 s3 AWS S3 Protocol Implementation worksforme
Projects
None yet
Development

No branches or pull requests

2 participants