From c2aeabc738021b6587c77cc23ac6bf7babe6d672 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Mon, 9 Oct 2023 15:00:33 -0400 Subject: [PATCH] comment --- ..._e3bc14a173600b86c5875d90228aea8b._comment | 25 +++++++++++++++++++ 1 file changed, 25 insertions(+) create mode 100644 doc/bugs/__96__git_annex_info__96___hangs_with_git_special_remote/comment_1_e3bc14a173600b86c5875d90228aea8b._comment diff --git a/doc/bugs/__96__git_annex_info__96___hangs_with_git_special_remote/comment_1_e3bc14a173600b86c5875d90228aea8b._comment b/doc/bugs/__96__git_annex_info__96___hangs_with_git_special_remote/comment_1_e3bc14a173600b86c5875d90228aea8b._comment new file mode 100644 index 0000000000..b6685e786b --- /dev/null +++ b/doc/bugs/__96__git_annex_info__96___hangs_with_git_special_remote/comment_1_e3bc14a173600b86c5875d90228aea8b._comment @@ -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. +"""]] -- 2.30.2