Joey Hess dad4be97c2 speculatively use remote's configured chunk size as a fallback ... When a special remote has chunking enabled, but no chunk sizes are recorded (or the recorded ones are not found), speculatively try chunks using the configured chunk size. This makes eg, git-annex fsck --from remote be able to fix up the location log of a file that the git-annex branch does not indicate is stored on the remote. Note that fsck does *not* fix up the chunk log to indicate the chunk size. So, changing the chunk config of the remote after that will still prevent accessing the chunks stored on it. Maybe fsck should, but I wanted to start with this and see if it's needed.		2020-10-22 13:11:06 -04:00
..
Chunked	audit all uses of SomeException to avoid catching async exceptions	2020-06-05 15:16:57 -04:00
AWS.hs	include credPairRemoteFields in RemoteConfigParsers	2020-01-15 10:57:45 -04:00
Chunked.hs	speculatively use remote's configured chunk size as a fallback	2020-10-22 13:11:06 -04:00
Encryptable.hs	fix a further bug	2020-06-16 18:14:36 -04:00
ExportImport.hs	external backends wip	2020-07-29 15:23:18 -04:00
Git.hs	convert TopFilePath to use RawFilePath	2019-12-09 15:07:21 -04:00
Hooks.hs	make retrieveKeyFile and retrieveKeyFileCheap throw exceptions	2020-05-13 17:07:07 -04:00
Http.hs	make storeKey throw exceptions	2020-05-13 14:03:00 -04:00
Messages.hs	update licenses from GPL to AGPL	2019-03-13 15:48:14 -04:00
P2P.hs	make removeKey throw exceptions	2020-05-14 14:11:05 -04:00
ReadOnly.hs	convert renameExport to throw exception	2020-05-15 15:08:09 -04:00
Special.hs	make removeKey throw exceptions	2020-05-14 14:11:05 -04:00
Ssh.hs	use uninterruptibleMask	2020-06-09 15:02:56 -04:00