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

Re: git fails updating submodule only if --quiet is specified

From
Jeff King <peff@peff.net>
Date
Mar 22, 2016, 22:25 UTC
Message-ID
<20160322222501.GA29577@sigill.intra.peff.net>
In-Reply-To
<CAGZ79kb0izRAZoQaDxTjKNz0VFEBqbkCSmro2pHm_kmLpJk0mw@mail.gmail.com>
On Tue, Mar 22, 2016 at 02:38:34PM -0700, Stefan Beller wrote:
Show 8 quoted lines
> On Tue, Mar 22, 2016 at 11:22 AM, Stefan Beller <sbeller@google.com> wrote:
> > However lookingat your logs, I would suspect it is an error in git
> > clone instead, as that is the
> > last command which has the --quiet flag passed through the stack.
> 
> git clone --no-checkout --quiet --separate-git-dir tmp_gitdir
> git://git.busybox.net/buildroot tmp_workdir
> fails as a standalone program as well, so let's debug that.
I think you can simplify this quite a bit to just:
  git clone --quiet git://git.busybox.net/buildroot

That breaks, but works without --quiet. Presumably the problem is on the server side, as we see the remote end hang up (and using different versions of git on the client does not seem to help).

It seems to fail consistently for me around 2.4s, which makes me think we're hitting some kind of timeout. I'd suspect a bug in the keep-alive code in upload-pack, but that shouldn't have kicked in by then.

I guess the next step is to try to reproduce with a local client/server, and then bisect the server version.

-Peff
Previous: Stefan BellerNext: Jeff King
Message 6 of 8 in “git fails updating submodule only if --quiet is specified”
  1. Marcus TMar 22, 2016
  2. Marcus TMar 22, 2016
  3. Stefan BellerMar 22, 2016
  4. Stefan BellerMar 22, 2016
  5. Stefan BellerMar 22, 2016
  6. Jeff KingMar 22, 2016
  7. Jeff KingMar 22, 2016
  8. Stefan BellerMar 22, 2016

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.