git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: 2.54.0: fyi: endless loop at 100% CPU

From
Michael Montalbo <mmontalbo@gmail.com>
Date
Jun 27, 2026, 19:39 UTC
Message-ID
<CAC2Qwm+48Gpj=AWHzx-nO00bwVfuYoGiwd=3gExbybcOyHC45Q@mail.gmail.com>
Steffen Nurpmeso <steffen@sdaoden.eu> writes:
Show 5 quoted lines
> I have no idea and i am not looking either, but my scripted update
> of tracked repos stuck, and i can a hundred percent reproduce an
> endless loop that consumes hundred percent CPU by doing
>
>  git ls-remote https://gitlab.xiph.org/xiph/opus.git
Hello, thank you for the report.

When I tried reproducing this locally I was able to get a response eventually, though there was what seemed to be a stall mid-way through the response from the server. After looking closer, the linked repo appears to be behind Anubis[1] which may be rate-limiting and/or blocking the requests from your script. FWIW, running:

GIT_TRACE_CURL=1 git ls-remote https://gitlab.xiph.org/xiph/opus.git 2>&1

locally showed the TLS handshake starting then pausing for a significant period of time before eventually completing the request successfully. Maybe running the command with the trace will show something on your end?

Also, here are some other potentially relevant configuration options [2][3]:
  git -c http.version=HTTP/1.1 \
  -c http.lowSpeedLimit=1000 \
  -c http.lowSpeedTime=10

[1] https://anubis.techaro.lol/ [2] https://git-scm.com/docs/git-config#Documentation/git-config.txt-httpversion [3] https://git-scm.com/docs/git-config#Documentation/git-config.txt-httplowSpeedLimit

Next: Steffen Nurpmeso
Message 1 of 4 in “Re: 2.54.0: fyi: endless loop at 100% CPU”
  1. Michael MontalboJun 27, 2026
  2. Steffen NurpmesoJun 27, 2026
  3. Michael MontalboJun 27, 2026
  4. Steffen NurpmesoJun 28, 2026

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.