restic/internal/repository
Michael Eischer 1adf28a2b5 repository: properly return invalid data error in LoadUnpacked
The retry backend does not return the original error, if its execution
is interrupted by canceling the context. Thus, we have to manually
ensure that the invalid data error gets returned.

Additionally, use the retry backend for some of the repository tests, as
this is the configuration which will be used by restic.
2023-01-14 17:57:02 +01:00
..
testdata
doc.go
fuzz_test.go repository: Remove empty cleanup functions in tests 2022-12-11 11:06:25 +01:00
key.go identify keys by ID and not name 2022-10-15 16:07:43 +02:00
packer_manager_test.go
packer_manager.go all: Replace some errors.Wrap calls by errors.WithStack 2022-12-17 09:41:07 +01:00
packer_uploader.go
repack_test.go repository: Remove empty cleanup functions in tests 2022-12-11 11:06:25 +01:00
repack.go prune: Use a single CountedBlobSet to track blobs 2022-10-22 18:45:12 +02:00
repository_internal_test.go
repository_test.go repository: Remove empty cleanup functions in tests 2022-12-11 11:06:25 +01:00
repository.go repository: properly return invalid data error in LoadUnpacked 2023-01-14 17:57:02 +01:00
testing.go repository: properly return invalid data error in LoadUnpacked 2023-01-14 17:57:02 +01:00