使用NTLM代理的git克隆在解析deltas后挂起 [英] git clone with NTLM proxy hangs after resolving deltas

查看:476
本文介绍了使用NTLM代理的git克隆在解析deltas后挂起的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我在这里看到很多涉及git和代理主题的问题,但他们都没有解决我的问题。
我从Bitbucket中克隆了一个git仓库。一切从我的家庭网络工作正常,但挂在我们正在使用代理与NTLM身份验证的工作。查看git clone命令的输出:

  $ git clone https://my_user@bitbucket.org/my_user/my_project.git --verbose 
克隆到'my_project'中...
'https://my_user@bitbucket.org'的密码:
POST git-upload-pack(174字节)
远程:计数对象:548,完成。
remote:压缩对象:100%(367/367),完成。
remote:总计548(delta 216),重用0(delta 0)
接收对象:100%(548/548),5.28 MiB | 533 KiB / s,完成。
解决三角洲问题:完成100%(216/216)。

git clone命令始终挂在解析变化量。



我的设置:


  • Windows 7 64位msysgit 1.8.0

  • 配置代理:

      $ git config --global http.proxy http:// MY_DOMAIN \\\\ \\ my_user:my_password @ http-proxy:8080 






  • 看起来问题在某种程度上与git对象大小有关,因为当我只有少量文件在我的仓库中时,git clone才开始工作。

    解决方案

    我用Git 1.7.11创建了同样的问题。我所有从GitHub克隆的尝试都会导致没有文件的挂起进程。我尝试了 verify-pack 技巧以及类似问题中的许多其他建议,但是没有任何结果。



    我想也许这个已经在Git的最新版本中得到改进或修复,所以我升级到了1.8.3。宾果,现在它可以工作,我可以克隆!


    I saw here many questions covering git and proxy topics but none of them solves my problem. I am cloning a git repository from Bitbucket. Everything works fine from my home network but hangs at work where we are using proxy with NTLM authentication. See the output of git clone command:

    $ git clone https://my_user@bitbucket.org/my_user/my_project.git --verbose
    Cloning into 'my_project'...
    Password for 'https://my_user@bitbucket.org':
    POST git-upload-pack (174 bytes)
    remote: Counting objects: 548, done.
    remote: Compressing objects: 100% (367/367), done.
    remote: Total 548 (delta 216), reused 0 (delta 0)
    Receiving objects: 100% (548/548), 5.28 MiB | 533 KiB/s, done.
    Resolving deltas: 100% (216/216), done.
    

    git clone command always hangs on "Resolving deltas".

    My setup:

    • Windows 7 64-bit with msysgit 1.8.0
    • proxy configured:

      $git config --global http.proxy http://MY_DOMAIN\\\my_user:my_password@http-proxy:8080
      


    It seems that the problem is somehow related to git object size because git clone used to work at the very beginning when I had few files only in my repository.

    解决方案

    I hit the same issue, with Git 1.7.11. All my attempts to clone from GitHub result in a hung process with no files. I tried the verify-pack trick and many other suggestions in similar questions but nothing worked.

    I figured maybe this has been improved or fixed in the latest version of Git, so I upgraded to 1.8.3. Bingo, now it works, I can clone!

    这篇关于使用NTLM代理的git克隆在解析deltas后挂起的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆