fatal: unable to access Specs.git

[dumoko]

• I've read and understood the *CONTRIBUTING guidelines and have done my best effort to follow.

Report

What did you do?

We're trying to use a new pod, therefore we're trying to run pod repo update

What happened?

=> pod repo update
  Updating spec repo `master`
  $ /usr/local/bin/git pull --ff-only
  fatal: unable to access 'https://github.com/CocoaPods/Specs.git/': transfer closed with outstanding read data remaining

It happens all the day. What is the issue?

[jshier]

Yes, the specs repo is especially slow right now, and has been since last night. Finally time to move to sharded version?

[oozoofrog]

I'm testing just with 'git clone https://github.com/CocoaPods/Specs.git'.
It's not working too.

[andyyhope]

Having the same issue.
pod repo update --verbose

Updating spec repo `master`
  $ /usr/bin/git -C /Users/andyyhope/.cocoapods/repos/master pull --ff-only
  fatal: unable to access 'https://github.com/CocoaPods/Specs.git/': transfer closed with outstanding read data remaining

[chrisdhaan]

Im having the same issue. Have tried completely uninstalling and reinstalling. Any updates?

[qooarleo]

Same here, any update?

[bahadiraurea]

Any update please?

[orta]

Sharding the repo will bring down the stress on GitHub's servers ( as we mentioned in the blog post ) but it's a destructive move to both the Specs repo and the trunk db - which also forces everyone to migrate to 1.x versions of CocoaPods. So we don't want rush that.

Ideally, once we're sure that the the sharing has gone successfully, we can also look at reducing the amount of commits on the main branch, meaning that the commits transferred should be reduced.

We were planning on doing this post-1.1.0, as a lot of the work is already done - CocoaPods/trunk.cocoapods.org#187 - but the release is taking longer than expected, no-one works full time on CocoaPods., however it should be released very soon.

WRT the timeouts, only GitHub staff know the actual reason for why they are timing out I'm afraid. We've reached out to them. In order to avoid more +1s - I'm going to lock the thread however, last time this happened I had to do quite a lot of thread pruning.

My twitter DMs are open if you'd like to contact me privately about this.

[andyyhope]

Thanks Orta!

[bahadiraurea]

Thanks orta hope it will be resolved asap

[benasher44]

Just a heads up that this is happening soon!

http://blog.cocoapods.org/Sharding/

Cheers!

[orta]

And has happened 👍