fix handling of importtree-only remotes
Don't want to try to use these remotes as key/value remotes, which will surely fail. It only recently became possible for importtree to be set w/o exporttree, so before this code was ok. (cherry picked from commit 97599cb0f7f4115aa5a3e81a91ee3d1d6c52dc84)
This commit is contained in:
parent
e9db382308
commit
f62aee0525
4 changed files with 8 additions and 3 deletions
|
@ -30,7 +30,7 @@ type Reason = String
|
|||
- and numcopies settings.
|
||||
-
|
||||
- Skips trying to drop from remotes that are appendonly, since those drops
|
||||
- would presumably fail. Also skips dropping from exporttree remotes,
|
||||
- would presumably fail. Also skips dropping from exporttree/importtree remotes,
|
||||
- which don't allow dropping individual keys.
|
||||
-
|
||||
- The UUIDs are ones where the content is believed to be present.
|
||||
|
@ -87,6 +87,7 @@ handleDropsFrom locs rs reason fromhere key afile si preverified runner = do
|
|||
| uuid r `S.notMember` slocs = go fs rest n
|
||||
| appendonly r = go fs rest n
|
||||
| exportTree (config r) = go fs rest n
|
||||
| importTree (config r) = go fs rest n
|
||||
| checkcopies n (Just $ Remote.uuid r) =
|
||||
dropr fs r n >>= go fs rest
|
||||
| otherwise = pure n
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue