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

Existing S3 metadata not visible #10647

Closed
cyberduck opened this issue Mar 7, 2019 · 7 comments
Closed

Existing S3 metadata not visible #10647

cyberduck opened this issue Mar 7, 2019 · 7 comments
Assignees
Labels
bug fixed s3 AWS S3 Protocol Implementation
Milestone

Comments

@cyberduck
Copy link
Collaborator

2602672 created the issue

Existing metadata is not visible while browsing S3 files in Cyberduck.

Adding or updating records works, but these changes are not visible in Cyberduck after a refresh.

Attached are screenshots from Cyberduck and the S3 console for the same file.

I'm not sure when this broke, but it was working at some point in the past.


Attachments

@cyberduck
Copy link
Collaborator Author

@dkocher commented

I cannot reproduce this error. Can you confirm you are running version 6.9.4.

@cyberduck
Copy link
Collaborator Author

2602672 commented

I am running 6.9.4.

I've tried a few older versions as well. It seems to be working as expected in 6.8.3 and earlier, but not working in 6.9 and later.

@cyberduck
Copy link
Collaborator Author

2602672 commented

One note, folder metadata appears normally for me in 6.9.4, but file metadata does not.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Regression from 24714ad.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

In c33c4b3.

@cyberduck
Copy link
Collaborator Author

2602672 commented

Fix confirmed!

Works as expected in the 7.0.0.30235 snapshot build. Thanks!

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Ticket retargeted after milestone deleted

@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