Nick Craig-Wood fa43f10af2 filescom: fix corrupted uploads after a retried upload error ...

When an upload failed with a retryable error the pacer retried the
whole upload with the same input stream. The stream had already been
consumed by the first attempt so the retry uploaded an empty file.

This fixes it by using CallNoRetry for the upload, as the other
backends do, so retryable errors are returned wrapped in a RetryError
for the caller to retry the upload with a fresh stream.

It also makes 5xx errors from the upload storage servers retryable.
These come back from the SDK as a different error type to API errors
so were not being retried at all.

2026-09-05 12:14:46 +01:00

..

filescom_test.go

filescom: add Files.com backend

2024-08-15 17:00:39 +01:00

filescom.go

filescom: fix corrupted uploads after a retried upload error

2026-09-05 12:14:46 +01:00