git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Workshop BLE <workshop.ble@gmail.com>
To: git@vger.kernel.org
Subject: git hangs forever after updating to V.2.45.1
Date: Tue, 28 May 2024 11:01:14 +0200	[thread overview]
Message-ID: <CANXjuPnUr81bKGMqZMvDjVZ+1suddoR5-8-SZn8W4EehW5-siw@mail.gmail.com> (raw)

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


Please review the rest of the bug report below.
You can delete any lines you don't wish to share.


[System Info]
git version:
git version 2.45.1.windows.1
cpu: x86_64
built from commit: 965b16798dab6962ada5b0d8cf0dca68f385c448
sizeof-long: 4
sizeof-size_t: 8
shell-path: /bin/sh
feature: fsmonitor--daemon
uname: Windows 10.0 22631
compiler info: gnuc: 13.2
libc info: no libc information available
$SHELL (typically, interactive shell): C:\Program Files\Git\usr\bin\bash.exe


[Enabled Hooks]
not run from a git repository - no hooks to show

             reply	other threads:[~2024-05-28  9:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-28  9:01 Workshop BLE [this message]
2024-06-03 22:37 ` git hangs forever after updating to V.2.45.1 brian m. carlson

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=CANXjuPnUr81bKGMqZMvDjVZ+1suddoR5-8-SZn8W4EehW5-siw@mail.gmail.com \
    --to=workshop.ble@gmail.com \
    --cc=git@vger.kernel.org \
    /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 NNTP newsgroup(s).