Fix: retryable error on final chunk request fails deferred length uploads #794
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I noticed while testing out retry behavior on a deferred length upload that if the final chunk request received a retryable error response from the server, the retry would fail due to a missing
Upload-Length
header and the upload would not be recoverable. I was able to stably reproduce the issue by pointing to a local tusd server set to 409 whenever theUpload-Length
header was present.As far as I can tell, nothing hangs on
this._uploadLengthDeferred
being set tofalse
on the final chunk request, and it's necessary for it to be present on a retry so the retry gains theUpload-Length
header, so the simplest solution is just to remove this line.