Skip to main content
14 events
when toggle format what by license comment
Dec 17, 2024 at 8:09 comment added T.H. I hit the similar error even with shallow clone --depth=1 , after SSH setup described in github doc, the git can complete clone without the error.
Apr 3, 2024 at 11:47 comment added Death-is-the-real-truth This works for me: stackoverflow.com/questions/78267333/…
Dec 30, 2022 at 8:29 comment added Anju mohan changing http.postBuffer 524288000 worked for me.Thank you
Oct 9, 2020 at 23:02 comment added Martin Braun Beware: I experienced several issues with npm publish when raising the postBuffer. When I set it down to 50000000, issues were gone. The default value is 1000000, by the way.
Jul 20, 2020 at 11:02 comment added Ilias.P worked for me too for pulling a large solution via a slow vpn connection
Jun 18, 2020 at 20:57 comment added cregox after all great steps listed here, git clone ssh://[email protected]/<repository base>/<repository name>.git is the only clone command that worked with me. and there's no need to reference the ssh is in the command at all (in case you're also wondering like i was).
Mar 25, 2020 at 21:25 comment added Negar Zamiri Changing http.postBuffer worked for me - thanks!
Oct 23, 2019 at 14:58 comment added http8086 that's nice, but anyone knows why that happens for 100% cloned?
Dec 5, 2017 at 12:56 comment added Tanvir Singh if error is still there , you should edit your ssh config file vi /users/username/.ssh/config and add serverAliveInterval 120 and exit the vi using wq (to save and exit). This will actually prevent the server from timeout and connection break errors.
Oct 31, 2017 at 9:03 comment added thangdc94 Change from HTTP to SSH work for me. Config http.postBuffer didn't work.
Mar 3, 2017 at 7:47 review Suggested edits
Mar 3, 2017 at 11:06
Sep 8, 2016 at 13:55 history edited Vy Do CC BY-SA 3.0
added 99 characters in body
Aug 2, 2016 at 15:32 vote accept Vy Do
Aug 1, 2016 at 15:47 history answered Vy Do CC BY-SA 3.0