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

followup

Browse source
This commit is contained in:
Joey Hess 2018-11-12 11:49:44 -04:00
parent 398bac4530
commit 911f75232b
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
1 changed files with 24 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

24
doc/bugs/multiple_ssh_prompts__44___and_thread_blocked_indefinitely_in_an___63____63____63___transaction/comment_3_eea08486fa9669bd197eb9e957b65ef8._comment Normal file
View file

@ -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
<https://github.com/datalad/datalad/issues/2988> 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`.
"""]]