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

Re: Git wire protocol v2 fails fetching shallow changes with `pack has XXX unresolved deltas` on large repos with lots of tags Inbox x

From
JTJonathan Tan <jonathantanmy@google.com>
Date
Oct 17, 2018, 20:53 UTC
Message-ID
<20181017205340.190036-1-jonathantanmy@google.com>
In-Reply-To
<CAGY-PBgsG-T3JY=awszwGMpFx+jDx-a1FcV0s6vR067bSqgZaA@mail.gmail.com>
Show 5 quoted lines
> No changes are needed in mirrored repository. Crash happens both with
> 2.18.0 and 2.19.1 git versions. Having repository locally is not
> required but reduces test runtime, you can quite reliably reproduce
> issue when fetching over net directly from chromium.orgbypassing
> mirroring step.
Do you have the reproduction steps for this? If I run
  git -c protocol.version=2 fetch --tags \
    https://chromium.googlesource.com/chromium/src \
    +refs/heads/*:refs/remotes/origin/* --depth=1

repeatedly in the same repository, it succeeds. (And I've checked with GIT_TRACE_PACKET that it uses protocol v2.)

Previous: Jonathan TanNext: Arturas Moskvinas
Message 3 of 4 in “Git wire protocol v2 fails fetching shallow changes with `pack has XXX unresolved deltas` on large repos with lots of tags Inbox x”
  1. Arturas MoskvinasOct 11, 2018
  2. Jonathan TanOct 13, 2018
  3. Jonathan TanOct 17, 2018
  4. Arturas MoskvinasOct 19, 2018

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.