[Cyberduck-trac] [Cyberduck] #11752: S3 Empty prefix causing "Failure to read attributes of <prefix>"

[Cyberduck]

#11752: S3 Empty prefix causing "Failure to read attributes of <prefix>"
-------------------------------------------------+------------------------
 Reporter:  freakk                               |         Owner:  dkocher
     Type:  defect                               |        Status:  closed
 Priority:  high                                 |     Milestone:
Component:  s3                                   |       Version:  7.10.0
 Severity:  critical                             |    Resolution:  wontfix
 Keywords:  failure attributes empty prefix 404  |  Architecture:  Intel
 Platform:  macOS 10.15                          |
-------------------------------------------------+------------------------

Comment (by freakk):

 ''"You can workaround this by making sure you always have at least one
 object under the prefix specified as the default path."''
 Sounds a  bit hacky, especially since lifecycle rules will cause the files
 to be deleted eventually.

 ''"This is by design to make this work as a filesystem in ​Mountain Duck
 when we want to fail when attempting to read directory contents for
 arbitrary prefixes."''
 I'm not aware of Mountain Duck, but shouldn't Cyberduck keep returning the
 empty list as it used to, letting Mountain Duck fail on empty payload if
 it needs to?
 It's odd that a feature on a new product introduces a breaking change on
 an existing product that should be unrelated.

 Anyway, this issue has been quickly dismissed as "wontfix", so we can only
 tell the users who reported it to stick to aws cli or aws sdk.

--
Ticket URL: <https://trac.cyberduck.io/ticket/11752#comment:3>
Cyberduck <https://cyberduck.io>
Libre FTP, SFTP, WebDAV, S3 & OpenStack Swift browser for Mac and Windows