22

I have been trying to clone the aosp repo, it worked fine last week but hasn't been for the last two days. I narrowed it down to the deqp dependecy. With the however I got multiple errors but always resulting in "fatal: fetch-pack: invalid index-pack output". Last try resulted in this:

   /run/me/j/d/a/deqp    master  git config http.postBuffer 524288000
   /run/me/j/d/a/deqp    master  git fetch --unshallow               ✔ 
remote: Finding sources: 100% (126764/126764)
remote: Total 126764 (delta 86667), reused 126714 (delta 86667)
Receiving objects: 100% (126764/126764), 2.33 GiB | 6.12 MiB/s, done.
error: inflate: data stream error (incorrect data check)
fatal: serious inflate inconsistency
fatal: fetch-pack: invalid index-pack output

What could be the problem?

Improve this question
6
  • Does this answer your question? fatal: early EOF fatal: index-pack failed Commented Dec 6, 2021 at 21:59
  • 1
    No sadly it does not. I tried that already. The final result remains the same: "fatal: fetch-pack: invalid index-pack output" Commented Dec 6, 2021 at 22:05
  • 5
    This is usually caused by a proxy (https redirector) that has a bug and corrupts your data. You can try using ssh, if that's available, or remove the "security appliance" that's making your network super-secure by making it not work. :-) Commented Dec 7, 2021 at 3:51
  • Just as an addition, I haven't found a solution to the problem as it just went away a couple of days later. For anyone still looking at this question, a lot of the solutions are pretty good. Commented Sep 24, 2022 at 10:32
  • I hit this in a CircleCI Orb...Upgrading the docker container size solved it for me, using the resource_class attribute. Commented Jan 31, 2023 at 13:13

7 Answers 7

Reset to default
14

I also encountered this problem on macOS Big Sur 11.6.1, and I run ulimit -n unlimited and ulimit -f unlimited to resolve this. Increase the value of packedGitLimit or packedGitWindowSize and packSizeLimit on gitconfig did not work for me.

Improve this answer
Sign up to request clarification or add additional context in comments.

Comments

11

If the proj is too big, try using --depth=1 to solve.

Improve this answer

Comments

11

Try to run the following:

git config pack.windowMemory 10m

git config pack.packSizeLimit 20m

then retry the git clone.

Improve this answer

3 Comments

I'm trying to clone a repo but your solution suggests that you already cloned the repo: $ git config pack.windowMemory 10m fatal: not in a git directory
The above worked for me by applying it at --global level
is the windowMemory being 1/2 the packSizeLimit important? is windowMemory even necessary?
3

This solved my problem.

git pull --depth=1 {repo} {branch}
Improve this answer

1 Comment

This didn't work for me; but I think the repo I'm trying to clone (github.com/qgis/QGIS) is just VERY big. This may well be the reason why I get this error.
0

In my case, this is works

git reset --hard
git clean -dfx
git fetch --all --depth 1
Improve this answer

Comments

0

Got same problem in container. Increased memory and CPU limits. Problem dissapeared

Improve this answer

Comments

0

I had the some problem, in WebStorm and also in Terminal.

When no solution worked for me, I tried deleting the repo folder, and the OS thrown warning that it can't delete file and can't read them, but it still correctly placed the files in the bin.

After downloading the repo again the problem hasn't come back.

Improve this answer

1 Comment

As it’s currently written, your answer is unclear. Please edit to add additional details that will help others understand how this addresses the question asked. You can find more information on how to write good answers in the help center.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.