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

"Failure to read attributes of..." when replacing a deleted file #9962

Closed
cyberduck opened this issue Jun 2, 2017 · 2 comments
Closed

"Failure to read attributes of..." when replacing a deleted file #9962

cyberduck opened this issue Jun 2, 2017 · 2 comments
Assignees
Labels
bug fixed s3 AWS S3 Protocol Implementation
Milestone

Comments

@cyberduck
Copy link
Collaborator

b8707ec created the issue

I've been able to duplicate this problem using three different computers and both .png and .jpg files.

System : MAC OS 10.12.4
Cyberduck v 6.0.0, 6.0.1, and 6.0.4

This seems to only happen with a bucket that has versioning turned on, and I tested using Cyberduck v5.4.4, and it did not happen while following the same process.

Steps:

  1. Add a file to an a S3 bucket that has versioning enabled
  2. Delete the file from the AS3 bucket
  3. Try to add the file back to the same AS3 bucket

Consistently, when we try this, we get an error that says:

"Failure to read attributes of flie_name.jpg. The specified key does not exist. Please contact your web hosting service provider for assistance."

The only way we have found to work around this is to rename the file to anything but what it was originally – or – turning on Hidden Files and deleting the greyed out version of the file that has a size other than "--" first, and then the one that has the size of "--" second.

You can overwrite the file fine (though it will not override permissions; not sure if that is a different bug or not). But if you delete the file, you must either get rid of the hidden files, or rename the file to something else.


Attachments

@cyberduck
Copy link
Collaborator Author

@dkocher commented

In e01c222.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Milestone renamed

@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