Skip to content

Conversation

@optlsnd
Copy link
Contributor

@optlsnd optlsnd commented Feb 25, 2025

If a multipart upload is started with a custom part size, the part size must be set in the request to /multipart/start/. Otherwise, the default 5 MB part size is used, which causes the subsequent request to /multipart/complete/ to fail:

{
    "error":
    {
        "status_code": 400,
        "content": "Can not complete upload. Wrong parts size?",
        "error_code": "MultipartFileCompletionFailedError"
    }
}

…tipart upload

If a multipart upload is started with a custom part size, the part size must be set in the request to `/multipart/start/` via `part_size`. Otherwise, the default 5 MB part size is used, which causes the subsequent request to `/multipart/complete/` to fail with the following error:

```
{
    "error":
    {
        "status_code": 400,
        "content": "Can not complete upload. Wrong parts size?",
        "error_code": "MultipartFileCompletionFailedError"
    }
}
```
@optlsnd optlsnd requested a review from nd0ut February 25, 2025 10:01
@nd0ut nd0ut force-pushed the fix/multipart-start-chunk-size branch from a1a6c22 to 07cfa79 Compare February 25, 2025 13:12
@nd0ut nd0ut merged commit 13d4c84 into master Feb 25, 2025
1 check passed
@nd0ut nd0ut deleted the fix/multipart-start-chunk-size branch February 25, 2025 13:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

3 participants