From: Richard H Lee <ricardohenrylee@gmail.com>
To: cygwin@cygwin.com
Subject: Git status delay
Date: Sat, 18 Nov 2017 21:13:00 -0000 [thread overview]
Message-ID: <092c4159-1f86-a64a-6ae1-c9909ef4ef90@gmail.com> (raw)
I have an issue with git where it hangs for 10 to 20 seconds on several
commands, including "git status". For me this is reproducible on a fresh
install of Cygwin x64 in Windows 7.
I get the feeling I am doing something wrong on my end as "git status"
is a very commonly used command, yet I see no mentions of this on the
Cygwin mailing list.
Using gdb I can see git hang in the function validate_headref on an
lstat call. validate_headref pretty much does what it says and validates
the HEAD reference file. validate_headref is called multiple times for
different candidate paths for the HEAD reference file, e.g. ".git/HEAD"
etc. For some reason the path "//HEAD" is checked and this is causing a
delay. Paths starting with "//" are treated in Cygwin as CIFS paths and
the delay comes from the timeout when Windows tries to resolve the
hostname "HEAD" to a server.
Subsequent executions of "git status" return immediately as I guess the
resolution of "HEAD" as a hostname is cached.
I don't recall having this problem previously.
Does anyone else experience this issue?
Richard
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next reply other threads:[~2017-11-18 21:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-18 21:13 Richard H Lee [this message]
2017-11-20 10:04 ` Richard H Lee
2017-11-20 14:33 ` cyg Simple
2017-11-20 17:05 ` Andrey Repin
2017-11-21 10:27 ` Adam Dinwoodie
2017-12-05 14:14 ` Dawid Ferenczy
2017-12-05 17:00 ` Dawid Ferenczy
2017-12-11 23:36 ` Richard H Lee
2017-12-12 16:41 ` cyg Simple
2017-12-11 17:19 ` Dawid Ferenczy
2017-12-11 21:38 ` Adam Dinwoodie
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=092c4159-1f86-a64a-6ae1-c9909ef4ef90@gmail.com \
--to=ricardohenrylee@gmail.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).