Re: Git status delay
- Date: Mon, 11 Dec 2017 14:37:38 +0100
- From: Dawid Ferenczy <ferenczy@xxxxxxxx>
- Subject: Re: Git status delay
Original message "Re: Git status delay" from "Adam Dinwoodie
(adam@xxxxxxxxxxxxx)" sent 21. listopadu 2017, 11:27:28,
msgid:20171121102728.GM20681@xxxxxxxxxxxxx (3557 bytes):
> Your analysis is spot-on: Git is trying to find the directory that
> contains all the metadata for the current working copy, and traversing
> up the directory structure to do so. In circumstances I haven't managed
> to characterise (I don't see this problem) it sometimes tries to parse
> //HEAD -- on most POSIX systems, this is equivalent to /HEAD, but on
> Cygwin it refers to the UNC path \\HEAD, which Windows attempts to look
> up on the network. That network lookup is the cause of the delay you're
> (I believe this is a bug in Git, on the grounds that (a) Git in general
> supports POSIX systems and giving special meaning to paths starting with
> `\\` is allowed, if unusual, POSIX behaviour, and (b) Git specifically
> supports Cygwin, and this is very well documented Cygwin behaviour.)
exactly! I can confirm it. This is a screenshot from SysInternals' Process
You can see that it hanged for about 30 seconds trying to open the file
"\\HEAD\PIPE\wkssvc" which obviously failed with the BAD NETWORK PATH error.
On my system, it always hangs for the same amount time, it's most likely a
It just suddenly started to happen (I have a Git status in my prompt so I
noticed it when my shell started to behave extremely slowly). I have tried to
update both Cygwin and Git and it didn't help.
Also, it's happening even outside of any repository.
I would also say it's more likely a Git's issue than Cygwin's.
Senior web applications developer
PGP key ID: 0xA864A330EE1FE92B
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple