GitLab克隆错误RPC失败；curl 56请求的URL返回错误:401 [英] GitLab clone error RPC failed; curl 56 The requested URL returned error: 401

问题描述

使用GitLab和Git客户端版本-2.22.0.最近，我们已将与音频/视频相关的文件上传到我们的存储库中，当前存储库大小已增加到4.5 GB.因此，即使现在我们也无法克隆它.

Using GitLab and Git Client version as - 2.22.0. recently we have uploaded audio/video related files into our repository, currently the repository size increased to 4.5 GB. Due to this now even we are unable to clone it.

在克隆时，我们都无法克隆以下错误.

The following error being getting while cloning none of us able to clone.

githost/tmp$ git clone https://pic-gitlab.com/pic_code/network-mm.git
Cloning into 'network-mm'...
Username for 'https://pic-gitlab.com': labuser
Password for 'https://[e-mail]':
remote: Enumerating objects: 3695, done.
remote: Counting objects: 100% (3695/3695), done.
remote: Compressing objects: 100% (3337/3337), done.
error: RPC failed; curl 56 GnuTLS recv error (-110): The TLS connection was non-properly terminated.
fatal: the remote end hung up unexpectedly
fatal: early EOF
fatal: index-pack failed
Error(s) during clone:
git clone failed: exit status 128

尝试以下命令，但无济于事.

Tried below commands, however couldn’t help.

git config --global http.postBuffer 1048576000
git clone --depth=1 https://pic-gitlab.com/pic_code/network-mm.git

我们将不胜感激.

推荐答案

这似乎与旧的(2013年)GnuTLS副作用，也在这里见过.

首先检查问题是否在Git 2.22上仍然存在.

Check first if the issue persists with Git 2.22.

然后，尝试并与GitLab支持人员联系，要求从他们那侧删除该大文件.

Then, try and contact GitLab support to request for that huge file to be deleted on their side.

这篇关于GitLab克隆错误RPC失败；curl 56请求的URL返回错误:401的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！