You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
I enabled preserving modification date and then uploaded a new file to a S3 bucket. I deleted it, which created a delete marker. I deleted the previous version, i.e. the file itself, which completed successfully. I then deleted the delete marker, but it just creates a new delete marker.
Expected behavior
Before enabling the preservation of the modification date, I was able to delete a delete marker. I'm still able to on another installation of Cyberduck using the same profile but without the above changes to enable preserving modification date.
Desktop (please complete the following information):
OS: Windows 11
Cyberduck Version: 9.0.4 (42232)
Log Files
Delete and list was over 2000 lines long, so just extracted delete. cyberduck.log
Additional context
The text was updated successfully, but these errors were encountered:
As indicated by @Fydon this cannot be reproduced with the default AWS S3 connection profile but with the S3 (Timestamps) profile that has set s3.listing.metadata.enable=true. In this case file attributes are retrieved for every file using HEAD1 which is not supported for delete markers and causes us to dismiss the version ID.
I first installed the snapshot version just before and waited for the next release. When I checked for update, the window immediately disappeared even when there was a new release found to update to. Closing the app and openning it again prompted for the update, allowing me to update.
Describe the bug
I enabled preserving modification date and then uploaded a new file to a S3 bucket. I deleted it, which created a delete marker. I deleted the previous version, i.e. the file itself, which completed successfully. I then deleted the delete marker, but it just creates a new delete marker.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Before enabling the preservation of the modification date, I was able to delete a delete marker. I'm still able to on another installation of Cyberduck using the same profile but without the above changes to enable preserving modification date.
Desktop (please complete the following information):
Log Files
Delete and list was over 2000 lines long, so just extracted delete.
cyberduck.log
Additional context
The text was updated successfully, but these errors were encountered: