-
Notifications
You must be signed in to change notification settings - Fork 147
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
413 Payload Too Large when recursive remove a large directory #281
Comments
I would appreciate if, while digging, you also helped improve the code to dig out the actual error from the general HttpError case. Note that I have deleted large numbers of files in a single call before. |
I just checked, and the batchsize parameter is only available in the latest version. Unfortunately the latest version is unusable due to #279 |
Let's get that issue fixed, then. Did you try #280?
Since we can now send many requests concurrently, there is less of a need to pack them into large batches. Indeed, this very issue shows the problem. I don't know what an optimal batch-size would be... |
I didn't know the new version automatically did many calls at once, that's a great improvement (as well as asyncio support!). I will try out the PR, didn't see that last week. |
When calling rm(path, recursive=True), the request fails without an actual error response:
When digging deeper:
<Response [413]>
This happens basically on large directories.
The text was updated successfully, but these errors were encountered: