All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bagas Sanjaya <bagasdotme@gmail.com>
To: mingli zhang <zmlfoolishfish@gmail.com>, git@vger.kernel.org
Cc: Jonathan Tan <jonathantanmy@google.com>,
	"brian m. carlson" <sandals@crustytoothpaste.net>
Subject: Re: [bug]fatal: fetch-pack: invalid index-pack output
Date: Fri, 1 Sep 2023 18:15:06 +0700	[thread overview]
Message-ID: <ZPHHuiFn3v06hhVe@debian.me> (raw)
In-Reply-To: <50B3E989-0405-4B05-9940-D3943C62260A@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2340 bytes --]

On Sun, Aug 14, 2022 at 05:09:13AM +0800, mingli zhang wrote:
> HI,
> 
> At some point, I exec git pull/fetch/clone will got a fatal message:
> 
> ```
> 
> fatal: fetch-pack: invalid index-pack output
> 
> ```
> 
> I use git 2.36.1 on MacOS Monterey 12.3.1
> 
> ```
> git --version
> 04:51:36.776640 git.c:459 trace: built-in: git version
> git version 2.36.1
> 
> ```
> 
> Example:
> 
> ```
> 
> zml@localhashdata postgres % git pull -r
> 04:53:33.553655 git.c:459 trace: built-in: git pull -r
> 04:53:33.640927 run-command.c:654 trace: run_command: git merge-base --fork-point refs/remotes/origin/REL_14_STABLE REL_14_STABLE
> 04:53:33.651808 run-command.c:654 trace: run_command: git fetch --update-head-ok
> 04:53:33.658822 git.c:459 trace: built-in: git fetch --update-head-ok
> 04:53:33.683642 run-command.c:654 trace: run_command: unset GIT_PREFIX; GIT_PROTOCOL=version=2 ssh -o SendEnv=GIT_PROTOCOL git@github.com 'git-upload-pack '\''postgres/postgres.git'\'''
> remote: Enumerating objects: 16843, done.
> remote: Counting objects: 100% (16231/16231), done.
> remote: Compressing objects: 100% (4164/4164), done.
> 04:53:40.822310 run-command.c:654 trace: run_command: git index-pack --stdin -v --fix-thin '--keep=fetch-pack 70208 on localhashdata' --pack_header=2,10035
> 04:53:40.828465 git.c:459 trace: built-in: git index-pack --stdin -v --fix-thin '--keep=fetch-pack 70208 on localhashdata' --pack_header=2,10035
> remote: Total 10035 (delta 8554), reused 7150 (delta 5805), pack-reused 0
> Receiving objects: 100% (10035/10035), 6.93 MiB | 2.42 MiB/s, done.
> fatal: fetch-pack: invalid index-pack output
> 
> ```
> 
> I try to config memory or use git pull -r --depth 1, but didn’t help.
> 
> My git config is
> 
> ```
> [core]
> packedGitLimit = 512m
> packedGitWindowSize = 512m
> compression = 0
> 
> [pack]
> deltaCacheSize = 2047m
> packSizeLimit = 2047m
> windowMemory = 2047m
> ```
> 
> And the code dir permission is
> 
> ```
> drwxrwxrwx
> 
> ```
> 
> Any suggestions ?

Related discussion is in [1] with the fix for OpenSSL users is in [2].
Please test.

[1]: https://lore.kernel.org/git/ZPCL11k38PXTkFga@debian.me/
[2]: https://lore.kernel.org/git/20230901020928.M610756@dcvr/

-- 
An old man doll... just what I always wanted! - Clara

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2023-09-01 11:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-13 21:09 [bug]fatal: fetch-pack: invalid index-pack output mingli zhang
2023-09-01 11:15 ` Bagas Sanjaya [this message]
2023-09-01 16:53   ` Junio C Hamano
2023-09-07  9:06     ` Bagas Sanjaya

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=ZPHHuiFn3v06hhVe@debian.me \
    --to=bagasdotme@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=jonathantanmy@google.com \
    --cc=sandals@crustytoothpaste.net \
    --cc=zmlfoolishfish@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.