-
Notifications
You must be signed in to change notification settings - Fork 31
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
listObjects lack retry mechanism #118
Comments
Please provide more detailed reproducible steps, along with sample code. |
i pull a lot of file from the server for backup operation(about 300K). i fix the issue by add simple retry operation in list conduit, and add http managerSetting timeout duration.
|
i upload the related code to github: |
Thanks for the report, we will take a look. |
@clojurians-org We understand the problem - the library does not implement any retry functionality for request timeouts. We will add this feature. Thanks again for the report! |
@clojurians-org Could you try out version 1.3.0? It contains a retry mechanism. |
yes, it's work now. the ConnectInfo(..) data constructor didn't export, the connectIsSecure can't be used.
|
@clojurians-org We have a fix here #121 - we will make a minor release after it is merged. |
@clojurians-org Version 1.3.1 has change #121 and should solve your problem. |
i fetch huge file size from server, it will contains 3 * 10^5 file number.
when i run listObjects, it report Request Timeout.
The text was updated successfully, but these errors were encountered: