You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have done a quick search against the latest code on develop branch, the IFMatch prediction wasn't used in multi-part downloading task.
if someone patches or replaces the file during downloading(large file or slow network), the result may be end up as a mix-in of multiple revisions, especially when chunk size is small.
The text was updated successfully, but these errors were encountered:
Just to clarify, the idea is to take the ETag value we get during the head_object call and pass it through all the get_object() calls. If we get a 412 error then we mark the object as a failed (or retry again from the beginning). Is that right?
I have done a quick search against the latest code on develop branch, the IFMatch prediction wasn't used in multi-part downloading task.
if someone patches or replaces the file during downloading(large file or slow network), the result may be end up as a mix-in of multiple revisions, especially when chunk size is small.
The text was updated successfully, but these errors were encountered: