Re: git hangs forever after updating to V.2.45.1

From: brian m. carlson <sandals@crustytoothpaste.net>
Date: Jun 3, 2024, 22:37 UTC
Message-ID: <Zl5FsMHT0k53TMJk@tapette.crustytoothpaste.net>
In-Reply-To: <CANXjuPnUr81bKGMqZMvDjVZ+1suddoR5-8-SZn8W4EehW5-siw@mail.gmail.com>

On 2024-05-28 at 09:01:14, Workshop BLE wrote:

Show 31 quoted lines

> What did you do before the bug happened? (Steps to reproduce your issue)
> Upgraded git-bash (windows) to latest version 2.45.1
> 
> What did you expect to happen? (Expected behavior)
> git works as usual
> 
> What happened instead? (Actual behavior)
> git pull and git clone just hangs forever when remote is dev.azure.com
> (did not try any other remote)
> 
> What's different between what you expected and what actually happened?
> see above
> 
> Anything else you want to add:
> When executing with GIT_TRACE=1 GIT_TRACE_PACKET=1 GIT_CURL_VERBOSE=1
> it can be seen, that git connects successfully to remote, but hangs
> after a cuple of this lines:
> 10:51:38.026547 git.c:465               trace: built-in: git config
> --null --type=path http.dev.azure.com.cookieFile
> 10:51:38.065783 exec-cmd.c:243          trace: resolved executable
> dir: C:/Program Files/Git/mingw64/libexec/git-core
> 10:51:38.071783 git.c:465               trace: built-in: git config
> --null --type=path http.https://azure.com.cookieFile
> 10:51:38.110297 exec-cmd.c:243          trace: resolved executable
> dir: C:/Program Files/Git/mingw64/libexec/git-core
> 10:51:38.116296 git.c:465               trace: built-in: git config
> --null --type=path http.azure.com.cookieFile
> 10:51:38.155881 exec-cmd.c:243          trace: resolved executable
> dir: C:/Program Files/Git/mingw64/libexec/git-core
> 10:51:38.161881 git.c:465               trace: built-in: git config
> --null --type=path http.cookieFile

Can you provide an affected repository that's publicly available? I don't know of one myself that reproduces the problem.

Can you also tell us what version you tried that _didn't_ have this problem?

I also don't see any calls to `http.cookiefile` or related paths on my system, which is a Debian sid/amd64 system using a next version. Is this maybe from a credential helper that you're using? If you're using Git Credential Manager Core, which comes with Git for Windows, it looks like you may be seeing https://github.com/git-ecosystem/git-credential-manager/issues/1620.

If so, you probably want to follow up on that issue or with the Git for Windows maintainers, since that credential helper isn't a part of core Git, and as such, there's nothing we can do to fix it.

-- 
brian m. carlson (they/them or he/him)
Toronto, Ontario, CA