How can I fix this serious git clone error?

[eduardz097]

Select Topic Area

Question

Body

I tried the following:

E:\Workspace\Blockchain>git clone https://github.com/substrate-developer-hub/substrate-node-template.git
Cloning into 'substrate-node-template'...
remote: Enumerating objects: 2185, done.
remote: Counting objects: 100% (91/91), done.
remote: Compressing objects: 100% (55/55), done.
Receiving objects: 94%(2062/2185), 3.18 MiB | 9.00 KiB/s

After a 20 minute delay at 94%, the result is:

E:\Workspace\Blockchain>git clone https://github.com/substrate-developer-hub/substrate-node-template.git
Cloning into 'substrate-node-template'...
remote: Enumerating objects: 2185, done.
remote: Counting objects: 100% (91/91), done.
remote: Compressing objects: 100% (55/55), done.
error: 6546 bytes of body are still expectediB | 11.00 KiB/s
fetch-pack: unexpected disconnect while reading sideband packet
fatal: early EOF
fatal: fetch-pack: invalid index-pack output

How can I fix it?

[valentinojosh]

Hi!

There could be a lot of different things going on so I'm going to give you a general list and hopefully something helps!

• If you're using a VPN, disconnect from it
• Restart router and computer
• Try on a different network
• Try from a different workspace
• Try: git clone --depth=1 https://github.com/substrate-developer-hub/substrate-node-template.git

If none of those steps work you might want to consider downloading the repo as a zip and working with it locally.

Hope this helps!

[brandenvs]

Truly hilarious.

[raggi]

It's not a network issue, it's a bug in the now extremely stale windows ssh release that has been fixed but they've failed to ship a production release:

PowerShell/Win32-OpenSSH#1322

The fix has been in for nearly a year now but has been missed in every update.

You can update to their beta with winget install Microsoft.OpenSSH.Beta

[isaacobenzy]

Having same issue and i have restart the machine like 6 times today

[souvik666]

Having same issue and i have restart the machine like 6 times today

Did you found a solution

[venkateshkolisetty-ctl]

Worked for me after disconnecting VPN. Thank you.

[queenofcorgis]

Thanks for posting in the GitHub Community, @oliver-pyon !

We're happy you're here. You are more likely to get a useful response if you are posting your question in the applicable category, the Issues category is solely related to conversations around the GitHub products Issues and Projects. I've gone ahead and moved it for you.

[HassanSj]

The error you're encountering, "fetch-pack: unexpected disconnect while reading sideband packet" along with "fatal: early EOF" and "fatal: fetch-pack: invalid index-pack output," often indicates a network or connectivity issue while cloning a Git repository from a remote server. Here are some steps to help you fix this issue:

1. Check Your Internet Connection: Ensure that your internet connection is stable and not experiencing interruptions. Slow or unstable internet connections can lead to incomplete downloads.

2. Retry the Clone: Sometimes, network issues are temporary. Retry the clone command to see if the issue resolves itself.

git clone https://github.com/substrate-developer-hub/substrate-node-template.git

3. Use SSH: If you continue to face issues with HTTPS cloning, consider using SSH to clone the repository. Ensure that you've set up an SSH key pair and added the public key to your GitHub account.

git clone [email protected]:substrate-developer-hub/substrate-node-template.git

4. Increase Buffer Sizes: You can try increasing Git's buffer sizes to allow for larger transfers. You can do this by setting the following configuration values:

git config --global http.postBuffer 524288000  # Set a larger buffer size
git config --global core.compression 0         # Disable compression

5. Use a Git Client: If the issue persists, consider using a Git client like GitKraken, Sourcetree, or GitHub Desktop, which often have built-in features to handle network issues more gracefully.

6. Check GitHub Status: Occasionally, GitHub itself may experience issues. You can check the GitHub Status page (https://www.githubstatus.com/) to see if there are any ongoing incidents that might be affecting repository access.

7. Try Cloning Later: If you suspect that the issue is on the GitHub server's side, it may be worth trying the clone operation at a different time.

8. Contact GitHub Support: If none of the above solutions work, and you continue to experience issues, consider reaching out to GitHub support for assistance with the specific repository or server-related problems.

9. Check Proxy Settings: If you are behind a corporate firewall or using a proxy server, ensure that your Git configuration reflects the correct proxy settings.

Keep in mind that the error message you're seeing is often related to network issues, so troubleshooting your network connectivity is a critical step in resolving this problem.

[isaacobenzy]

I am also having same but when i clone different repo's it works

[mdranacse19]

Thank you so much. you save me a lot of time.

[VDIAN01]

This is based on network issue. I also faced same issue while connecting mobile data So connected wifi issue is resolved.

[virajbhutada]

[queenofcorgis]

Hi @virajbhutada ,

We’ve clarified our stance on using generative AI tools like ChatGPT within our Community via this announcement. Please review the guidelines to ensure your post meets them as failure to adhere to those rules can result in action taken by our moderator team.  You can read our updated Code of Conduct and the announcement for more details. Thank you for helping us maintain an authentic and beneficial space for everyone.

[watchpoints]

change https to ssh

[w0nd3r365]

Tried so many proposed solutions from stackoverflow, but this is the only one that worked when cloning github.com/jellyfin/jellyfin.org

[RaymanMartin]

I got the relativly issue like.

Receiving objects: 100% (1103339/1103339), 29.19 GiB | 71.13 MiB/s, done. error: inflate: data stream error (incorrect data check) fatal: serious inflate inconsistency fatal: fetch-pack: invalid index-pack output

This git repository is about 30G，its a Aosp git repository

this issue raise persistently, And i had try plently of method, but this issue still there.

First : modify git config file.
core.packedgitlimit=51200m core.packedgitwindowsize=52100m core.compression=0 pack.windowmemory=8096m pack.packsizelimit=8096m pack.deltacachesize=8096m ssh.postbuffer=524288000 core.repositoryformatversion=0 core.filemode=true core.bare=false core.logallrefupdates=true http.postbuffer=524288000

didnt work for me

Second: acrroding to stack overflow，I had try modify the system property like ulimit file
real-time non-blocking time (microseconds, -R) unlimited core file size (blocks, -c) 0 data seg size (kbytes, -d) unlimited scheduling priority (-e) 0 file size (blocks, -f) unlimited pending signals (-i) 191275 max locked memory (kbytes, -l) 6130312 max memory size (kbytes, -m) unlimited open files (-n) 2460000 pipe size (512 bytes, -p) 8 POSIX message queues (bytes, -q) 819200 real-time priority (-r) 0 stack size (kbytes, -s) 8192 cpu time (seconds, -t) unlimited max user processes (-u) 191275 virtual memory (kbytes, -v) unlimited file locks (-x) unlimited
didnt work for me

Third: try to use git init and git remote add origin xxxurl, then git fetch --all --depath 1
didnt work for me

If theres any other solution？Or maybe i should change the network?

DeviceInfo:
Ubuntu：22.0.4
Git：2.34.1
Memory：48G ram and 50G swapFile size

[aliqramraju-git]

Same here. I have tried all the methods mentioned still having the problem.

[MuhammedKAldin]

mere network issue. connect to mobile data and you will O.K

[alhassan-cse]

good answer

[sundayglee]

Use git clone --recursive

[akshaydhardubey]

you can use google colab or some other environment for git clone
then export the files using

!tar -czf file_name.tar.gz {'file_path'}

replace file_path with the file path you want to export and file_name with the selective file name

[chrisdenton-ct]

I get this same issue on my iMac all the time. Cloning works fine outside of GitHub Desktop, and even GitHub Desktop works on a Macbook Air which is on the same WiFi.

[Hasan-Mir]

Had the same problem, I imported the repo from Github to Gitlab and cloned the project from Gitlab, which worked without any issues.
On Github, the problem was resolved only after switching from WiFi to mobile network.

[SobanSiraj]

Git: 1683 bytes of body are still expected

[SobanSiraj]

no answer

[SobanSiraj]

github fetch issue

[3iv4ns]

mine worked after restarting my laptop and switched to mobile connection

[zaheerahmad33]

I tried all of the above nothing worked for me

What worked for me

I updated the git bash to version 2.46.0 and issue solved!

[faroukcharkas]

I was getting this error while connected to an airport network, but then I turned on my VPN (NordVPN connected to Chicago) and I was able to download just fine.