Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

git clone fatal error : RPC failed , The remote end hung up unexpectedly, early EOF

Tags:

git

unix

i'm trying to clone a repository and start using it so i tape u

$ git clone https://github.com/VirtuOR/OpenTRILL

the cloning begins

Cloning into 'OpenTRILL'...
remote: Counting objects: 46419, done.
remote: Compressing objects: 100% (42140/42140), done.

but it ends with the following error

error: RPC failed; result=18, HTTP code = 200MiB | 55 KiB/s    
fatal: The remote end hung up unexpectedly
fatal: early EOF
fatal: index-pack failed

Any help please

like image 232
asma Avatar asked Aug 31 '13 13:08

asma


People also ask

How do you solve fatal the remote end hung up unexpectedly?

Solution. To solve the issue, change the settings of your buffer so that you have enough space available. You can increase the buffer value up to 2000000000.

What is http postBuffer?

postBuffer is about: Maximum size in bytes of the buffer used by smart HTTP transports when POSTing data to the remote system. For requests larger than this buffer size, HTTP/1.1 and Transfer-Encoding: chunked is used to avoid creating a massive pack file locally.

What does git clone depth do?

"Clone depth" is a feature of git to reduce server load: Instead of cloning the complete repository (as usually done with git), using clone depth just clones the last clone-depth-number revisions of your repository.

What is git shallow clone?

Git shallow clone lets you pull down just the latest commits, not the entire repo history. So if your project has years of history, or history from thousands of commits, you can select a particular depth to pull.


1 Answers

I know its late but here is the solution,

First,let's do a partial clone to truncate the amount of info coming down:

git clone --depth 1 <url>

it will clones the repository with the minimum git history. however,cloning with ‘–depth 1′ does not let you push your changed to your remote repo. Now fetch the rest with :

git fetch --depth=1000000
(Update Oct/3/2013) for git version >= 1.8.3,
git fetch --unshallow

note:

‘git fetch –unshallow’ is basically an alias for ‘git fetch –depth=2147483647′.

Pushing from a shallow clone isn’t guaranteed; the recommended workflow is to submit a patch(git format-patch) from your shallow clone. Though git clone manual states that a shallow clone cannot push, having a common commit history between your shallow clone and origin will allow the shallow clone to push through. But be warned that your shallow clone will be in trouble if the origin reworks the commit history.(source article: why-cant-i-push-from-a-shallow-clone).

like image 147
nitesh goel Avatar answered Oct 19 '22 02:10

nitesh goel