-
-
Notifications
You must be signed in to change notification settings - Fork 2k
Bundler::HTTPError: Network error while fetching #2769
Comments
The dependency API went down during the period you're talking about. There is a bug in the current version of Bundler that downloads tons of gemspecs needlessly when the dependency API is down. :/ The Dependency API is now back up, and the bug that downloads all the gemspecs is fixed in the latest version of Bundler. You can try the release candidate by running |
Thanks for the information. Good to know it's fixed in the latest version. Btw, http://status.rubygems.org/ was all green including Dependency API during that time. |
Hmm. I don’t actually know how the dependency API checker works, but the outage wasn’t full—the API was still responding to as many requests as it could, but failing to respond to enough of them that you hit at least one bad one. On Dec 19, 2013, at 11:27 PM, Christopher Rigor notifications@github.com wrote:
|
I was having this issue. After bundle installing many times with various levels of failure while fetching from "http://rubygems.org" and "https://rubygems.org" running "curl https://rubygems.org" failed as well. After running "curl https://rubygems.org --verbose" everything worked. |
@mgidea that sounds like it was just a temporary outage of rubygems.org or a problem on your network. |
We should probably rescue this error and say that we couldn't connect, check your network and status.rubygems.org and try again. On Wed, May 14, 2014 at 7:25 PM, Tim Moore notifications@github.com
|
Good idea! rubygems/bundler-features#53 |
I ran bundle install on a new Ubuntu 12.04 server. It was taking a long time (more than 15 minutes) and I didn't wait for it to finish.
Adding --verbose shows Bundler::HTTPError: Network error while fetching.
It then proceeds on fetching all (not just for the gems I need) gemspec.rz which would take a long time. It started with http://rubygems.org/quick/Marshal.4.8/_-1.0.gemspec.rz and after a few minutes it's still on gems starting with 'a'.
I found #2618, added --full-index and it worked.
I tried again just now (after 8 hours of the initial problem) by uninstalling libv8. bundle install --verbose works. It would still be good to know what happened and why --full-index fixes it.
More details at https://gist.github.com/crigor/7bd937ce9dd10d0a8c01.
The text was updated successfully, but these errors were encountered: