Nick Craig-Wood a06df7a2de protondrive: fix corrupted uploads after a retried upload error - fixes #9722 ...

When an upload failed part way through with a retryable error (eg a
502 from the block storage servers) the pacer retried the whole upload
call with the same input stream. The stream had already been partially
consumed, so the retry re-created the upload draft and committed just
the remainder of the stream as a complete file, silently truncating
it. With restic over serve restic this corrupted the repository as the
truncated pack was reported as successfully uploaded.

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.

2026-08-04 19:29:21 +01:00

..

protondrive_internal_test.go

protondrive: fix long hangs on permanent validation failures

2026-07-13 15:22:47 +01:00

protondrive_test.go

protondrive: add protondrive backend - fixes #6072

2023-07-22 10:46:21 +01:00

protondrive.go

protondrive: fix corrupted uploads after a retried upload error - fixes #9722

2026-08-04 19:29:21 +01:00