From 5c57440482264dd8911bb5835f9b3f14a696e686 Mon Sep 17 00:00:00 2001 From: Ilya_Shlyakhter Date: Wed, 5 Feb 2020 22:19:30 +0000 Subject: [PATCH] Added a comment: example of where retries could help --- .../comment_6_5a7771a6169caa90fd91bc6ea7b4fe3d._comment | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 doc/todo/more_extensive_retries_to_mask_transient_failures/comment_6_5a7771a6169caa90fd91bc6ea7b4fe3d._comment diff --git a/doc/todo/more_extensive_retries_to_mask_transient_failures/comment_6_5a7771a6169caa90fd91bc6ea7b4fe3d._comment b/doc/todo/more_extensive_retries_to_mask_transient_failures/comment_6_5a7771a6169caa90fd91bc6ea7b4fe3d._comment new file mode 100644 index 0000000000..51b9a693b3 --- /dev/null +++ b/doc/todo/more_extensive_retries_to_mask_transient_failures/comment_6_5a7771a6169caa90fd91bc6ea7b4fe3d._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="Ilya_Shlyakhter" + avatar="http://cdn.libravatar.org/avatar/1647044369aa7747829c38b9dcc84df0" + subject="example of where retries could help" + date="2020-02-05T22:19:26Z" + content=""" +As one example, I just had a `git-annex-copy` command fail twice with `git-annex: thread blocked indefinitely in an STM transaction`, then have the same command succeed (or at least get much further -- still running) on the third try. I can write my own wrappers to mask such errors, but a built-in implementation seems generally useful and would know better which failures are likely transient. +"""]]