From 28dc7d01decba408bb3db911a58f94842a279ae8 Mon Sep 17 00:00:00 2001 From: Ilya_Shlyakhter Date: Wed, 5 Feb 2020 16:59:44 +0000 Subject: [PATCH] Added a comment: retries due to locked index file --- .../comment_5_69b132f465851421acb7e5edf009995d._comment | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 doc/todo/more_extensive_retries_to_mask_transient_failures/comment_5_69b132f465851421acb7e5edf009995d._comment diff --git a/doc/todo/more_extensive_retries_to_mask_transient_failures/comment_5_69b132f465851421acb7e5edf009995d._comment b/doc/todo/more_extensive_retries_to_mask_transient_failures/comment_5_69b132f465851421acb7e5edf009995d._comment new file mode 100644 index 0000000000..e764bdd56b --- /dev/null +++ b/doc/todo/more_extensive_retries_to_mask_transient_failures/comment_5_69b132f465851421acb7e5edf009995d._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="Ilya_Shlyakhter" + avatar="http://cdn.libravatar.org/avatar/1647044369aa7747829c38b9dcc84df0" + subject="retries due to locked index file" + date="2020-02-05T16:59:40Z" + content=""" +\"A locked git index file does not prevent git-annex from making transfers\" -- by \"mask transient failures\" I meant all types of failures, not just transfers. So e.g. if concurrent operations fail due to contention for the index file lock, retries (after increasing, randomized intervals) could mask the failure. This would help especially for writing scripts/tools on top of git-annex. Logically, some operations -- like `git-annex-add` -- should never fail, and being able to assume that makes scripting easier. +"""]]