mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

avoid cleaning up move log when drop from remote fails

Browse source 
move: Improve resuming a move that succeeded in transferring the content,
but where dropping failed due to eg a network problem, in cases where
numcopies checks prevented the resumed move from dropping the object from
the source repository.

This was earlier done for moves that got interrupted during the drop stage.

Sponsored-by: Svenne Krap on Patreon
This commit is contained in:
Joey Hess 2022-06-09 15:26:25 -04:00
parent 13fc6a9b6a
commit 6d0b243d9d
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
3 changed files with 43 additions and 17 deletions
Download patch file Download diff file Expand all files Collapse all files

2
doc/bugs/move_that_fails_at_drop_stage_does_not_resume_correctly.mdwn
View file

@ -10,3 +10,5 @@ let the drop succeed.
The problem is that logMove runs its cleanup action in this case.
So the move.log gets the record of the move cleaned from it. It seems that
the cleanup action should avoid doing that when the move failed. --[[Joey]]
> [[fixed|done]] --[[Joey]]