write correctly complete_multipart_upload #30

Closed
opened 2021-02-19 11:10:12 +00:00 by lx · 1 comment
Owner

When calling complete_multipart_upload, client gives us the list of parts he sent.

Currently we do not check that we have these parts, we finish the upload based on what we are able to read at that point but some data might be lagging, in which case the completed upload might be marked with a wrong size.

When calling complete_multipart_upload, client gives us the list of parts he sent. Currently we do not check that we have these parts, we finish the upload based on what we are able to read at that point but some data might be lagging, in which case the completed upload might be marked with a wrong size.
lx added the
Bug
label 2021-02-19 11:10:13 +00:00
Author
Owner

Implemented in dev-0.2

Implemented in `dev-0.2`
lx closed this issue 2021-03-10 16:46:29 +00:00
lx added this to the 0.2 milestone 2021-03-10 16:48:31 +00:00
Sign in to join this conversation.
No Milestone
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: Deuxfleurs/garage#30
No description provided.