Closed alexfalkowski closed 9 years ago
Well, did you try running with the --full-index
flag as the error suggests doing?
Yes I did try running:
bundle outdated --full-index
I get:
Unknown switches '--full-index'
Eventually the command returns with the following error:
Fetching gem metadata from https://rails-assets.org/...
Fetching gem metadata from https://rubygems.org/...Retrying dependency api due to error (2/3): Bundler::HTTPError Net::HTTPUnprocessableEntity: Too many gems (use --full-index instead)
Retrying dependency api due to error (3/3): Bundler::HTTPError Net::HTTPUnprocessableEntity: Too many gems (use --full-index instead)
Net::HTTPNotFound: <?xml version="1.0" encoding="UTF-8"?>
<Error><Code>NoSuchKey</Code><Message>The specified key does not
exist.</Message><Key>quick/Marshal.4.8/acts_as_user-1.1.1.gemspec.rz</Key><RequestId>9FC422DAC93EA9A0</RequestId><HostId>Jtiq0QIyekC2RiICrqJECSnA10UlSE/b08fBFT3rrM7oFZW0I96Dpfg36OVaKiOVLUrxcbjUZ+s=</HostId></Error>
Since a Gemfile with a large number of gems is going to have those gems for the long term, can we make the --full-index
option persist for that Gemfile so that we don't need to write it every-time?
Maybe we can use an option in the Gemfile, or a dot file.
Bundler should be using --full-index
by default when there are 100 or
more gems. If that's not happening, there must be an edge case throwing it
off. More details would be helpful. If someone having this problem could
gist the output from bundle install --verbose
, that would help.
On Friday, 30 January 2015, Gonzalo Rodríguez-Baltanás Díaz < notifications@github.com> wrote:
Since a Gemfile with a large number of gems is going to have those gems for the long term, can we make the --full-index option persist for that Gemfile so that we don't need to write it every-time?
Maybe we can use an option in the Gemfile, or a dot file.
— Reply to this email directly or view it on GitHub https://github.com/bundler/bundler/issues/3367#issuecomment-72188415.
Sure, here it is: https://gist.github.com/Nerian/6ea104736101ad7bb103
same issue here, but --full-index fixed it.
--full-index indeed fixes it, but there are deployment PaaS's that only allow bundle install
(Cloud 66) as part of the build commands. Seems to make sense that Bundler should be able to determine how many gems need to be downloaded, and use --full-index on its own, without us explicitly using the flag, if need be.
This should be fixed in 1.7.13. Please try upgrading and let us know if you still have any problems.
Hi Team,
When I run:
The process just hangs reporting the following error:
Here is the output from running bundle env