From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 118674 invoked by alias); 5 Dec 2017 14:14:00 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 118661 invoked by uid 89); 5 Dec 2017 14:13:59 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=1.5 required=5.0 tests=BAYES_00,DATE_IN_PAST_96_XX,RCVD_IN_DNSWL_NONE autolearn=no version=3.3.2 spammy=msgid, NETWORK, H*R:D*cz, H*r:110 X-HELO: mail-wm0-f41.google.com Received: from mail-wm0-f41.google.com (HELO mail-wm0-f41.google.com) (74.125.82.41) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 05 Dec 2017 14:13:56 +0000 Received: by mail-wm0-f41.google.com with SMTP id f140so1526054wmd.2 for ; Tue, 05 Dec 2017 06:13:55 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:date:from:reply-to:message-id:to:subject :in-reply-to:references:mime-version:content-transfer-encoding; bh=0HgFbx3HZb8EGVf6IdkcC9akB9xbFIaRwvp+LDiDAcA=; b=KIXAYMvgZydhcZ2ko2xe0utyLN2WOEBg/S/L3iyXPZJVzqGT36DMlf3FWiN69s3Klg 8eic+PRMX4bt8/YcKkUc+hw+KV6XWOmldReUX0fhZfgb2FHqKHyZ6WNrNGijUS68dyZz LQe01wZOJLGELkrpP8dwp+p8O7VOcHRENGzWMQ0GvCrM+5h30zpR+FTmyehHfo7m0bfN +N5ibKmxpUTZmshXBFDCOnDrB/a9k2ZBdaF/v1+g2icQrsh4mrNZVcETzpK3wqOUkh4x Px5aVex9lz5EWCfd6ki1wyWENdoa+1vbVPWK7TkNNLzyAtWNEZWBisjyFsBFma2m5AoO 9bXw== X-Gm-Message-State: AKGB3mITveH8IrnlASByYlncl0L0ZCtu+THh27rKZ1zQEiS1anN98dzl 51lmkwT3DnmFmJj6TNmEq6j8Fp6lKJY= X-Google-Smtp-Source: AGs4zMbUvIjnl73MeLhs4UxdLZVzimfcIfk8JLnZzJQ6MBOfljsoDrLS8KujyUqVn7XmlXvgraOYjg== X-Received: by 10.28.27.206 with SMTP id b197mr10653659wmb.96.1512483234219; Tue, 05 Dec 2017 06:13:54 -0800 (PST) Received: from ferenczy-dell ([2a01:110:8012:1012::172]) by smtp.gmail.com with ESMTPSA id n32sm297270wrb.62.2017.12.05.06.13.53 (version=TLS1_1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Tue, 05 Dec 2017 06:13:53 -0800 (PST) Date: Tue, 05 Dec 2017 14:14:00 -0000 From: Dawid Ferenczy Reply-To: Dawid Ferenczy Message-ID: <1867005492.20171126014157@volny.cz> To: Adam Dinwoodie , cygwin@cygwin.com Subject: Re: Git status delay In-Reply-To: <20171121102728.GM20681@dinwoodie.org> References: <092c4159-1f86-a64a-6ae1-c9909ef4ef90@gmail.com> <20171121102728.GM20681@dinwoodie.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2017-12/txt/msg00041.txt.bz2 Original message "Re: Git status delay" from "Adam Dinwoodie (adam@dinwoodie.org)" sent 21. listopadu 2017, 11:27:28, msgid:20171121102728.GM20681@dinwoodie.org (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 > seeing. > (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.) Hi, exactly! I can confirm it. This is a screenshot from SysInternals' Process Monitor: https://ferenczy.cz/temp/cygwin-git-hang.png 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 timeout. 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. -- S pozdravem, Dawid Ferenczy Senior web applications developer ferenczy@volny.cz http://ferenczy.cz http://twitter.com/DawidFerenczy PGP key ID: 0xA864A330EE1FE92B ___________________________________ -- 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 From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 121625 invoked by alias); 5 Dec 2017 14:14:13 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 120920 invoked by uid 89); 5 Dec 2017 14:14:10 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=1.5 required=5.0 tests=BAYES_00,DATE_IN_PAST_96_XX,RCVD_IN_DNSWL_NONE autolearn=no version=3.3.2 spammy=msgid, NETWORK, H*R:D*cz, H*r:110 X-HELO: mail-wr0-f170.google.com Received: from mail-wr0-f170.google.com (HELO mail-wr0-f170.google.com) (209.85.128.170) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 05 Dec 2017 14:14:08 +0000 Received: by mail-wr0-f170.google.com with SMTP id l22so426785wrc.11 for ; Tue, 05 Dec 2017 06:14:08 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:date:from:reply-to:message-id:to:subject :in-reply-to:references:mime-version:content-transfer-encoding; bh=0HgFbx3HZb8EGVf6IdkcC9akB9xbFIaRwvp+LDiDAcA=; b=Mpam4ZMP+Trokqp7vMddVgZVQOxkKMI84Pn/CVIAVTequalrIH5QthqNENtOZfBbTV DRCu88YgBsHBPoox/9OCrnD60VDpqnLNnHnVceNx5ObBqeDLUs/P+mNhDnQho4s7LLc1 Z4y1wHoEqgWLebzvqd2t/GPDPJnDr8EAzSNWPT2Xk2fGIJdKVcvfjT/+jj1WLlyF9pxE n0EOi62UiCDHMz+kgB3dQaka6tLLElExOHKQfH63rtCfYf1SCNGFhsM7CTsn6RoSkuOC 0LwZf1ldMWGH+UQhPvlkzubB0S3R6NO1Rbc8BBDY51+/kwe/sTt+cWfet2HOWMEsJxNp ugXg== X-Gm-Message-State: AJaThX7xMRWR5VDbAVSTF1XqRBBWuCOSJVNt/ImYZ9SO1FYCPDOn1h+G 537jCO8kTaEP3FYyD4aDSdArrD/9Mt8= X-Google-Smtp-Source: AGs4zMYI8EdwgRdRChTkAcXC8SmBMj18AOfz+n9K5GYXEkVQY6wW3loezlQTW60t3yjqEjniyUUetA== X-Received: by 10.223.163.11 with SMTP id c11mr17256176wrb.214.1512483246696; Tue, 05 Dec 2017 06:14:06 -0800 (PST) Received: from ferenczy-dell ([2a01:110:8012:1012::172]) by smtp.gmail.com with ESMTPSA id v195sm592474wmf.25.2017.12.05.06.14.06 (version=TLS1_1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Tue, 05 Dec 2017 06:14:06 -0800 (PST) Date: Tue, 05 Dec 2017 17:00:00 -0000 From: Dawid Ferenczy Reply-To: Dawid Ferenczy Message-ID: <1867005492.20171126014157@volny.cz> To: Adam Dinwoodie , cygwin@cygwin.com Subject: Re: Git status delay In-Reply-To: <20171121102728.GM20681@dinwoodie.org> References: <092c4159-1f86-a64a-6ae1-c9909ef4ef90@gmail.com> <20171121102728.GM20681@dinwoodie.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2017-12/txt/msg00042.txt.bz2 Message-ID: <20171205170000.UNNqoscGfcuXxv8dEjiUMnqzUWQcOR_PfN1QK-Xi_0o@z> Original message "Re: Git status delay" from "Adam Dinwoodie (adam@dinwoodie.org)" sent 21. listopadu 2017, 11:27:28, msgid:20171121102728.GM20681@dinwoodie.org (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 > seeing. > (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.) Hi, exactly! I can confirm it. This is a screenshot from SysInternals' Process Monitor: https://ferenczy.cz/temp/cygwin-git-hang.png 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 timeout. 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. -- S pozdravem, Dawid Ferenczy Senior web applications developer ferenczy@volny.cz http://ferenczy.cz http://twitter.com/DawidFerenczy PGP key ID: 0xA864A330EE1FE92B ___________________________________ -- 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