-
-
Notifications
You must be signed in to change notification settings - Fork 2k
"Retrying dependency api due to error" issue #4222
Comments
Can you share the output of |
|
Out of curiosity, what does this line do in Gemfiles?
|
haha sorry, it's an internal gem server - just cut out the url |
Any updates? Still getting this for some projects continually, but some seem to be exempt from this. |
@segiddins is just me, or is our Postgres instance getting slower and slower? :/ it looks like we need to raise the statement timeout again |
Don't suppose anyone has had a chance to look at this? It is causing a few issues now when we try and run |
@jamesRaybould I think you can run |
Thanks for getting back to me, unfortunately running:
Still doesn't work and still errors out on the cache stage:
|
Again, seems to be an issue only when we're using the |
I hit this error just now, it has something to do with my gem server Note the freshly commented out line in my config.ru file:
I wonder if manually pushing |
Are there any action items here? It seems VMC is no longer maintained. Additionally, is it reproducible/still an issue with the latest version of bundler? ( |
I would chalk this up to a problem with geminabox, close the ticket and see if @tmharber comes back with fresh information. |
Hi all. I'm currently trying to do a bundle install for a particular project, but keep getting the error:
However, if I try following that URL, it takes a few seconds then downloads a 'dependencies' file, so clearly I'm able to hit it. It's also not a transient network error as I did a
bundle install
on the particular project (A) andbundle install
on another, unrelated project (B) at the same time - project A'sbundle install
failed but B'sbundle install
worked fine and didn't get these errors.One thing that works is if I use the suffix
--full-index
- in that case, it works perfectly, although it would be nice to know why it's failing without. Is it timing out when finding dependencies because there are too many gems possibly?I've tried running it on a different PC (two dev boxes and a deployment box) and get the same issue. Any ideas for what could be causing this? Using ruby-2.1.1 and bundler 1.11.2.
The text was updated successfully, but these errors were encountered: