{"thread":{"id":"61554","subject":"git hangs forever after updating to V.2.45.1","startedAt":"2024-05-28T09:01:27Z","lastAt":"2024-06-03T22:37:39Z","messageCount":2,"participants":["Workshop BLE","brian m. carlson"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"495737","messageId":"CANXjuPnUr81bKGMqZMvDjVZ+1suddoR5-8-SZn8W4EehW5-siw@mail.gmail.com","threadId":"61554","inReplyTo":null,"subject":"git hangs forever after updating to V.2.45.1","fromName":"Workshop BLE","fromEmail":"workshop.ble@gmail.com","sentAt":"2024-05-28T09:01:14Z","receivedAt":"2024-05-28T09:01:27Z","isPatch":false,"sender":{"key":"workshop.ble@gmail.com","avatar":null},"body":"What did you do before the bug happened? (Steps to reproduce your issue)\nUpgraded git-bash (windows) to latest version 2.45.1\n\nWhat did you expect to happen? (Expected behavior)\ngit works as usual\n\nWhat happened instead? (Actual behavior)\ngit pull and git clone just hangs forever when remote is dev.azure.com\n(did not try any other remote)\n\nWhat's different between what you expected and what actually happened?\nsee above\n\nAnything else you want to add:\nWhen executing with GIT_TRACE=1 GIT_TRACE_PACKET=1 GIT_CURL_VERBOSE=1\nit can be seen, that git connects successfully to remote, but hangs\nafter a cuple of this lines:\n10:51:38.026547 git.c:465               trace: built-in: git config\n--null --type=path http.dev.azure.com.cookieFile\n10:51:38.065783 exec-cmd.c:243          trace: resolved executable\ndir: C:/Program Files/Git/mingw64/libexec/git-core\n10:51:38.071783 git.c:465               trace: built-in: git config\n--null --type=path http.https://azure.com.cookieFile\n10:51:38.110297 exec-cmd.c:243          trace: resolved executable\ndir: C:/Program Files/Git/mingw64/libexec/git-core\n10:51:38.116296 git.c:465               trace: built-in: git config\n--null --type=path http.azure.com.cookieFile\n10:51:38.155881 exec-cmd.c:243          trace: resolved executable\ndir: C:/Program Files/Git/mingw64/libexec/git-core\n10:51:38.161881 git.c:465               trace: built-in: git config\n--null --type=path http.cookieFile\n\n\nPlease review the rest of the bug report below.\nYou can delete any lines you don't wish to share.\n\n\n[System Info]\ngit version:\ngit version 2.45.1.windows.1\ncpu: x86_64\nbuilt from commit: 965b16798dab6962ada5b0d8cf0dca68f385c448\nsizeof-long: 4\nsizeof-size_t: 8\nshell-path: /bin/sh\nfeature: fsmonitor--daemon\nuname: Windows 10.0 22631\ncompiler info: gnuc: 13.2\nlibc info: no libc information available\n$SHELL (typically, interactive shell): C:\\Program Files\\Git\\usr\\bin\\bash.exe\n\n\n[Enabled Hooks]\nnot run from a git repository - no hooks to show\n"},{"id":"496193","messageId":"Zl5FsMHT0k53TMJk@tapette.crustytoothpaste.net","threadId":"61554","inReplyTo":"CANXjuPnUr81bKGMqZMvDjVZ+1suddoR5-8-SZn8W4EehW5-siw@mail.gmail.com","subject":"Re: git hangs forever after updating to V.2.45.1","fromName":"brian m. carlson","fromEmail":"sandals@crustytoothpaste.net","sentAt":"2024-06-03T22:37:36Z","receivedAt":"2024-06-03T22:37:39Z","isPatch":false,"sender":{"key":"sandals@crustytoothpaste.net","avatar":"https://avatars.githubusercontent.com/u/497054?v=4"},"body":"On 2024-05-28 at 09:01:14, Workshop BLE wrote:\n> What did you do before the bug happened? (Steps to reproduce your issue)\n> Upgraded git-bash (windows) to latest version 2.45.1\n> \n> What did you expect to happen? (Expected behavior)\n> git works as usual\n> \n> What happened instead? (Actual behavior)\n> git pull and git clone just hangs forever when remote is dev.azure.com\n> (did not try any other remote)\n> \n> What's different between what you expected and what actually happened?\n> see above\n> \n> Anything else you want to add:\n> When executing with GIT_TRACE=1 GIT_TRACE_PACKET=1 GIT_CURL_VERBOSE=1\n> it can be seen, that git connects successfully to remote, but hangs\n> after a cuple of this lines:\n> 10:51:38.026547 git.c:465               trace: built-in: git config\n> --null --type=path http.dev.azure.com.cookieFile\n> 10:51:38.065783 exec-cmd.c:243          trace: resolved executable\n> dir: C:/Program Files/Git/mingw64/libexec/git-core\n> 10:51:38.071783 git.c:465               trace: built-in: git config\n> --null --type=path http.https://azure.com.cookieFile\n> 10:51:38.110297 exec-cmd.c:243          trace: resolved executable\n> dir: C:/Program Files/Git/mingw64/libexec/git-core\n> 10:51:38.116296 git.c:465               trace: built-in: git config\n> --null --type=path http.azure.com.cookieFile\n> 10:51:38.155881 exec-cmd.c:243          trace: resolved executable\n> dir: C:/Program Files/Git/mingw64/libexec/git-core\n> 10:51:38.161881 git.c:465               trace: built-in: git config\n> --null --type=path http.cookieFile\n\nCan you provide an affected repository that's publicly available?  I\ndon't know of one myself that reproduces the problem.\n\nCan you also tell us what version you tried that _didn't_ have this\nproblem?\n\nI also don't see any calls to `http.cookiefile` or related paths on my\nsystem, which is a Debian sid/amd64 system using a next version.  Is\nthis maybe from a credential helper that you're using?  If you're using\nGit Credential Manager Core, which comes with Git for Windows, it looks\nlike you may be seeing\nhttps://github.com/git-ecosystem/git-credential-manager/issues/1620.\n\nIf so, you probably want to follow up on that issue or with the Git for\nWindows maintainers, since that credential helper isn't a part of core\nGit, and as such, there's nothing we can do to fix it.\n-- \nbrian m. carlson (they/them or he/him)\nToronto, Ontario, CA\n"}]}