{"action":"created","issue":{"url":"https://api.github.com/repos/CocoaPods/CocoaPods/issues/4989","repository_url":"https://api.github.com/repos/CocoaPods/CocoaPods","labels_url":"https://api.github.com/repos/CocoaPods/CocoaPods/issues/4989/labels{/name}","comments_url":"https://api.github.com/repos/CocoaPods/CocoaPods/issues/4989/comments","events_url":"https://api.github.com/repos/CocoaPods/CocoaPods/issues/4989/events","html_url":"https://github.com/CocoaPods/CocoaPods/issues/4989","id":138907583,"number":4989,"title":"Issues Cloning Spec repo - GitHub taking a very long time to download changes to the Specs Repo","user":{"login":"jlubeck","id":3067603,"avatar_url":"https://avatars.githubusercontent.com/u/3067603?v=3","gravatar_id":"","url":"https://api.github.com/users/jlubeck","html_url":"https://github.com/jlubeck","followers_url":"https://api.github.com/users/jlubeck/followers","following_url":"https://api.github.com/users/jlubeck/following{/other_user}","gists_url":"https://api.github.com/users/jlubeck/gists{/gist_id}","starred_url":"https://api.github.com/users/jlubeck/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jlubeck/subscriptions","organizations_url":"https://api.github.com/users/jlubeck/orgs","repos_url":"https://api.github.com/users/jlubeck/repos","events_url":"https://api.github.com/users/jlubeck/events{/privacy}","received_events_url":"https://api.github.com/users/jlubeck/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/CocoaPods/CocoaPods/labels/t3:discussion","name":"t3:discussion","color":"E10288"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":52,"created_at":"2016-03-07T07:30:55Z","updated_at":"2016-03-08T17:02:51Z","closed_at":null,"body":"## What did you do?\r\n\r\nRun `pod setup`\r\n\r\n## What did you expected to happen?\r\n\r\nClone Spec repo master\r\n\r\n## What happened instead?\r\n\r\nIt only downloads a few bytes and then throws error:\r\n\r\n> fatal: unable to access 'https://github.com/CocoaPods/Specs.git/': transfer closed with outstanding read data remaining\r\n\r\n## Podfile\r\n\r\nNo Podfile yet\r\n\r\nI also tried cloning the repo manually or with the githhub desktop app with no avail. \r\nI´m having no issues cloning any other repo in github. Only with this one. Is it possible there is something wrong with it???\r\n\r\nThanks"},"comment":{"url":"https://api.github.com/repos/CocoaPods/CocoaPods/issues/comments/193869141","html_url":"https://github.com/CocoaPods/CocoaPods/issues/4989#issuecomment-193869141","issue_url":"https://api.github.com/repos/CocoaPods/CocoaPods/issues/4989","id":193869141,"user":{"login":"indygreg","id":342993,"avatar_url":"https://avatars.githubusercontent.com/u/342993?v=3","gravatar_id":"","url":"https://api.github.com/users/indygreg","html_url":"https://github.com/indygreg","followers_url":"https://api.github.com/users/indygreg/followers","following_url":"https://api.github.com/users/indygreg/following{/other_user}","gists_url":"https://api.github.com/users/indygreg/gists{/gist_id}","starred_url":"https://api.github.com/users/indygreg/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/indygreg/subscriptions","organizations_url":"https://api.github.com/users/indygreg/orgs","repos_url":"https://api.github.com/users/indygreg/repos","events_url":"https://api.github.com/users/indygreg/events{/privacy}","received_events_url":"https://api.github.com/users/indygreg/received_events","type":"User","site_admin":false},"created_at":"2016-03-08T17:02:50Z","updated_at":"2016-03-08T17:02:50Z","body":"@mhagger I suggest you look at the support I added to Mercurial for having servers \"redirect\" clients to pre-generated static bundles to facilitate more efficient cloning. This feature has been talked about on the Git mailing list but AFAIK hasn't yet manifested into patches. I believe that if it were in place GitHub wouldn't be seeing some of the scaling issues exhibited in this issue. (Although shallow clone is a hard problem given the challenges of caching something that is always changing.) I wrote a bit more on Mercurial's feature and its impact at Mozilla at https://news.ycombinator.com/item?id=11246458 and http://gregoryszorc.com/blog/2015/10/22/cloning-improvements-in-mercurial-3.6/."}}