From 911f75232b097a3f1b3b5ea0d464dcfec6a736a3 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Mon, 12 Nov 2018 11:49:44 -0400 Subject: [PATCH] followup --- ..._eea08486fa9669bd197eb9e957b65ef8._comment | 24 +++++++++++++++++++ 1 file changed, 24 insertions(+) create mode 100644 doc/bugs/multiple_ssh_prompts__44___and_thread_blocked_indefinitely_in_an___63____63____63___transaction/comment_3_eea08486fa9669bd197eb9e957b65ef8._comment diff --git a/doc/bugs/multiple_ssh_prompts__44___and_thread_blocked_indefinitely_in_an___63____63____63___transaction/comment_3_eea08486fa9669bd197eb9e957b65ef8._comment b/doc/bugs/multiple_ssh_prompts__44___and_thread_blocked_indefinitely_in_an___63____63____63___transaction/comment_3_eea08486fa9669bd197eb9e957b65ef8._comment new file mode 100644 index 0000000000..6799afbb23 --- /dev/null +++ b/doc/bugs/multiple_ssh_prompts__44___and_thread_blocked_indefinitely_in_an___63____63____63___transaction/comment_3_eea08486fa9669bd197eb9e957b65ef8._comment @@ -0,0 +1,24 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 3""" + date="2018-11-12T15:27:27Z" + content=""" +It certianly seems possible that +[[!commit 6ecd55a9fa4c64399b5ede3944bd2aa5f78cf0b1]] +could have introduced a locking problem causing such a crash, +assuming you are running that version (can't tell from your version string +due to the git rev not being one from the git-annex repo). + +As Andrew noted, the multiple ssh password prompt issue is expected if you +are using `GIT_SSH` or `GIT_SSH_COMMAND`. From discussion in + it seems like you might +be? + +The fact that it says +"(transfer already in progress, or unable to take transfer lock)" strongly +suggests they you have annex.pidlock set locally. It would be good to know +about this or other configuration. + +I have not had any luck reproducing the crash so far. I have tried setting +`GIT_SSH`, `GIT_ANNEX_USE_GIT_SSH`, and `annex.pidlock`. +"""]]