restic

Author	SHA1	Message	Date
Alexander Neumann	93210614f4	backend/retry: return worker function error and abort This is a bug fix: Before, when the worker function fn in List() of the RetryBackend returned an error, the operation is retried with the next file. This is not consistent with the documentation, the intention was that when fn returns an error, this is passed on to the caller and the List() operation is aborted. Only errors happening on the underlying backend are retried. The error leads to restic ignoring exclusive locks that are present in the repo, so it may happen that a new backup is written which references data that is going to be removed by a concurrently running `prune` operation. The bug was reported by a user here: https://forum.restic.net/t/restic-backup-returns-0-exit-code-when-already-locked/484	2018-02-24 13:26:13 +01:00
Igor Fedorenko	d58ae43317	Reworked Backend.Load API to retry errors during ongoing download Signed-off-by: Igor Fedorenko <igor@ifedorenko.com>	2018-02-16 21:12:14 -05:00
Igor Fedorenko	aa333f4d49	Implement RetryBackend.List() Signed-off-by: Igor Fedorenko <igor@ifedorenko.com>	2018-01-29 22:14:12 -05:00
Alexander Neumann	8dc952775e	backend: Correctly retry Save() calls Make sure the given reader is an io.Seeker and rewind it properly each time.	2017-10-17 21:46:38 +02:00