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

comment

Browse source
This commit is contained in:
Joey Hess 2023-10-09 15:00:33 -04:00
parent 4ec1694f89
commit c2aeabc738
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
1 changed files with 25 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

25
doc/bugs/__96__git_annex_info__96___hangs_with_git_special_remote/comment_1_e3bc14a173600b86c5875d90228aea8b._comment Normal file
View file

@ -0,0 +1,25 @@
[[!comment format=mdwn
username="joey"
subject="""comment 1"""
date="2023-10-09T18:50:00Z"
content="""
An easier way to see this behavior is:
git remote add foo 192.168.1.101:/dne
time git fetch foo
2:14.36elapsed
So I'm having difficulty seeing this as a bug in git-annex
particularly.
Yes, git-annex has to ssh once to new git remotes,
in order to determine their git-annex uuid. git-annex
info needs to know what uuids each remote has, so it's
certianly right that it does this.
Yes, if that fails git-annex falls back to a git fetch,
in order to determine if the remote is unavailable,
or if the remote is available but does not
have git-annex-shell installed. So it takes twice
as long to time out as the usual ssh tcp timeout.
"""]]