-
Notifications
You must be signed in to change notification settings - Fork 155
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
Cyberduck not listen files #1116
Comments
@francoricci Thanks for reporting this issue. I've confirmed on the latest (6.7.1.28683). Since other s3 clients works fine, there might be something wrong specific to the cyberduck latest. I'll dive into the cyberduck code from now on. Until I find the fix, would you like to keep using 6.2.2 cyberduck or try dragondisk (http://www.s3-client.com/) out as a GUI browser? |
I'll use the old version f CyberDuck until solution. |
It turns out that several comments I previously posted at here were wrong so I deleted those to keep comments clean. |
The reason why the latest cyberduck can't display any files but display folders stored in LeoFS is that they've changed the API retrieving the object list from https://docs.aws.amazon.com/AmazonS3/latest/API/RESTBucketGET.html to https://docs.aws.amazon.com/AmazonS3/latest/API/RESTBucketGETVersion.html. Since LeoFS has no yet supported GET Bucket Object versions API, any files have not been displayed on the latest cyberduck. At a first glance, the simple implementation which just returns the most recent objects can be implemented in quite less cost so that I'm going to implement it in that way and confirm if it works as expected. |
@francoricci I've just sent PR #1118 to fix the problem. The next stable release 1.4.3 will include the fix so once 1.4.3 comes out and you finish to upgrade LeoFS, you will be able to use the latest cyberduck. Please wait for a while. |
Great! Franco |
Until version 6.2.2 cyberduck listen files inside leofs buckets and directories.
Latest version of cyberduck can list only directories but now files inside is accessible.
The text was updated successfully, but these errors were encountered: