8206cd19c8
When the context used for a load operation is canceled, then the result is always an error independent of whether the file could be retrieved from the backend. Do not false positively trip the circuit breaker in this case. The old behavior was problematic when trying to lock a repository. When `Lock.checkForOtherLocks` listed multiple lock files in parallel and one of them fails to load, then all other loads were canceled. This cancelation was remembered by the circuit breaker, such that locking retries would fail.
10 lines
455 B
Text
10 lines
455 B
Text
Bugfix: Fix rare failures to retry locking a repository
|
|
|
|
Restic 0.17.0 could in rare cases fail to retry locking a repository if
|
|
one of the lock files failed to load. The lock operation failed with error
|
|
`unable to create lock in backend: circuit breaker open for file <lock/1234567890>`
|
|
|
|
The error handling has been fixed to correctly retry locking the repository.
|
|
|
|
https://github.com/restic/restic/issues/5005
|
|
https://github.com/restic/restic/pull/5011
|