Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

not cloning repo #18601

Closed
harisferoz-centric opened this issue May 11, 2024 · 1 comment
Closed

not cloning repo #18601

harisferoz-centric opened this issue May 11, 2024 · 1 comment
Labels
support Issues likely related to one person's environment or configuration

Comments

@harisferoz-centric
Copy link

The problem

I am unable to clone the repo since 24 hours as this message keeps on coming
error: RPC failed; curl 56 Failure when receiving data from the peer
error: 2739 bytes of body are still expected
fetch-pack: unexpected disconnect while reading sideband packet
fatal: early EOF
fatal: fetch-pack: invalid index-pack output
my internet speed is 80-100 MBPS

Release version

Version 3.3.17 (x64)

Operating system

Windows 10

Steps to reproduce the behavior

simply clone repository via github desktop

Log files

No response

Screenshots

No response

Additional context

No response

@steveward
Copy link
Member

@harisferoz-centric sorry to hear you're having trouble.

Network issues are tricky to diagnose, and there isn't much we can do from our end about them since the underlying Git operations are failing. Some users have had success running the following config option:

git config --global http.postBuffer 524288000

There are also some HTTP timeout config operations that may help, or at lease provide additional diagnosis about the timeout. One user previously had success with these commands:

git config --global http.lowSpeedLimit 1000
git config --global http.lowSpeedTime 20

The lowSpeedLimit configures the minimum bytes per second, and the lowSpeedTime is the number of seconds. If the operation is lower than that threshold for the set time it will timeout. Adjusting those values may help with timeouts.

If neither of those suggestions work it may be worth trying to set up a SSH key, which some users have had more success with when encountering network issues. You could then switch the remote URL to use SSH in GitHub Desktop by going to Repository > Repository Settings > Remote.

I'm going to close this out as there isn't anything we can do from our end to resolve this, but if you have any further questions let me know.

@steveward steveward added the support Issues likely related to one person's environment or configuration label May 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
support Issues likely related to one person's environment or configuration
Projects
None yet
Development

No branches or pull requests

2 participants