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

Re: Deadlock between git-remote-http and git fetch-pack

From
Junio C Hamano <gitster@pobox.com>
Date
Jan 27, 2017, 23:34 UTC
Message-ID
<xmqqefzoxeki.fsf@gitster.mtv.corp.google.com>
In-Reply-To
<CAFKYj4cMSK5nQ1nS66c4Opz8y7x+xQH+OdW8PTi7LmCiGBP1ZA@mail.gmail.com>
tsuna <tsunanet@gmail.com> writes:
Show 6 quoted lines
> While investigating a hung job in our CI system today, I think I found
> a deadlock in git-remote-http
> ...
> Here PID 27319 (git fetch-pack) is stuck reading on stdin, while its
> parent, PID 27317 (git-remote-http) is stuck reading on its child’s
> stdout.  Nothing has moved for like 2h, it’s deadlocked.

Hmph, would this be related to 296b847c0d ("remote-curl: don't hang when a server dies before any output", 2016-11-18) I wonder...

Previous: Jonathan Tan
Message 3 of 3 in “Deadlock between git-remote-http and git fetch-pack”
  1. tsunaJan 27, 2017
  2. Jonathan TanJan 27, 2017
  3. Junio C HamanoJan 27, 2017

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.