美文网首页
git clone报错

git clone报错

作者: vodaka | 来源:发表于2018-08-07 12:45 被阅读66次

    git clone报错

    error: RPC failed; curl 18 transfer closed with outstanding read data remaining

    fatal: The remote end hung up unexpectedly

    https://stackoverflow.com/questions/38618885/error-rpc-failed-curl-transfer-closed-with-outstanding-read-data-remaining

    the following solution works for me.

    $ git clone https://gitlab.intellicredit.cn/zhangshuangbi/safebox_1.git --depth 1

    $ cd safebox_1/

    $ git fetch --unshallow

    here is the original text from stackoverflow

    It happens more often than not, I am on a slow internet connection and I have to clone a decently-huge git repository. The most common issue is that the connection closes and the whole clone is cancelled.

    Cloning into 'large-repository'...

    remote: Counting objects: 20248, done.

    remote: Compressing objects: 100% (10204/10204), done.

    error: RPC failed; curl 18 transfer closed with outstanding read data remaining

    fatal: The remote end hung up unexpectedly

    fatal: early EOF

    fatal: index-pack failed

    After a lot of trial and errors and a lot of “remote end hung up unexpectedly” I have a way that works for me. The idea is to do a shallow clone first and then update the repository with its history.

    $ git clone http://github.com/large-repository --depth 1

    $ cd large-repository

    $ git fetch --unshallow

    the reason maybe slow internet connection or the repository is huge, because git use curl command for repository url is https

    相关文章

      网友评论

          本文标题:git clone报错

          本文链接:https://www.haomeiwen.com/subject/ouiovftx.html