This repository has been archived by the owner on Apr 14, 2021. It is now read-only.
-
-
Notifications
You must be signed in to change notification settings - Fork 2k
NoMethodError: undefined method `spec' for nil:NilClass #3558
Comments
This is in fact a bundler error. Posting patch. |
@digitalextremist could you please share the info requested in https://github.com/bundler/bundler/blob/master/ISSUES.md ? As it is, your issue doesn't really have enough in it to debug anything. Thanks! |
@segiddins: copied from the referenced issues: Output of
Resolved in #3559 |
digitalextremist
referenced
this issue
in rubygems/rubygems
Apr 11, 2015
The package object already caches the spec object, so we don't need to do it multiple times. Also introduce a consturctor for in-memory installations so that we can rm the `spec` setter method
Closing this in favor of #3559. |
janraasch
added a commit
to tolingo/file-convert
that referenced
this issue
Nov 10, 2015
as we ran into rubygems/bundler#3558 on older ruby versions on TravisCI
miketheman
added a commit
to miketheman/lita-jenkins
that referenced
this issue
Nov 13, 2015
The default bundler included in Travis CI Ruby environments is too old and contains a bug that triggers a failure and prevents testing. Refs: rubygems/bundler#3558 travis-ci/travis-ci#3531
miketheman
added a commit
to miketheman/lita-jenkins
that referenced
this issue
Nov 13, 2015
- The default bundler included in Travis CI Ruby environments is too old and contains a bug that triggers a failure and prevents testing. Refs: rubygems/bundler#3558 travis-ci/travis-ci#3531 - Add testing for Ruby 2.2.3, color rspec output
This was referenced Dec 7, 2015
tute
pushed a commit
to thoughtbot/factory_bot
that referenced
this issue
Dec 14, 2015
Builds are broken because the `bundler` version that Travis CI automatically uses at this time (`1.7.6`) is coming across an error that was fixed in a later version/release. Having an outdated version of `bundler` in the Travis CI builds is an ongoing issue and this is currently the easiest work-around. See: * rubygems/bundler#3558 * travis-ci/travis-ci#3531 [fixes #846]
dplummer
pushed a commit
to dplummer/json_api_client
that referenced
this issue
Dec 14, 2015
Builds are broken because the `bundler` version that Travis CI automatically uses at this time (`1.7.6`) is coming across an error that was fixed in a later version/release. Having an outdated version of `bundler` in the Travis CI builds is an ongoing issue and this is currently the easiest work-around. See: * rubygems/bundler#3558 * travis-ci/travis-ci#3531
DavidS
added a commit
to DavidS/puppet-syntax
that referenced
this issue
Dec 15, 2015
DavidS
added a commit
to DavidS/puppet-syntax
that referenced
this issue
Dec 15, 2015
MikaelSmith
pushed a commit
to MikaelSmith/puppet
that referenced
this issue
Dec 15, 2015
Install a newer version of bundler to avoid the issue at rubygems/bundler#3558. We ran into it several times with Ruby 1.9.3 runs.
ghost
mentioned this issue
Dec 18, 2015
dchandekstark
added a commit
to duke-libraries/ddr-models
that referenced
this issue
Dec 18, 2015
dchandekstark
added a commit
to duke-libraries/ddr-models
that referenced
this issue
Dec 18, 2015
Upgrade bundler b/c something like rubygems/bundler#3558
bquorning
added a commit
to zendesk/active_record_host_pool
that referenced
this issue
Dec 21, 2015
robwilliams
added a commit
to robwilliams/wisper-activerecord
that referenced
this issue
Dec 13, 2016
Forces the use of travis containers which have a newer version of bundler that do not have this bug. See rubygems/bundler#3558
tmr08c
added a commit
to tmr08c/roo-xls
that referenced
this issue
Jan 9, 2017
TravisCI builds are failing due to an [issue with bundler](rubygems/bundler#3558). One of the [suggested solutions](rubygems/bundler#3558 (comment)) was to use TravisCI's container-based infrastructure which has the added benefit of being faster. This commit updates `.travis.yml` to use the container-based infrastructure.
marcioj
added a commit
to inaka/assisted_workflow
that referenced
this issue
Jan 10, 2017
…nil:NilClass" Please see rubygems/bundler#3558 (comment)
yasaichi
added a commit
to yasaichi/gakubuchi
that referenced
this issue
Jan 31, 2017
jrafanie
added a commit
to jrafanie/binary_struct
that referenced
this issue
May 4, 2017
Resolves NoMethodError: undefined method `spec' for nil:NilClass on ruby 1.9.3 builds, see: rubygems/bundler#3558
collabital
pushed a commit
to collabital/yam
that referenced
this issue
Jul 6, 2017
2 tasks
donaldali
added a commit
to sendsonar/send_sonar_gem
that referenced
this issue
Sep 26, 2017
donaldali
added a commit
to sendsonar/send_sonar_gem
that referenced
this issue
Sep 26, 2017
See [bundler issue 3558](rubygems/bundler#3558)
5 tasks
daronco
added a commit
to mconf/bigbluebutton_rails
that referenced
this issue
Oct 4, 2017
petems
added a commit
to petems/petems-swap_file
that referenced
this issue
Oct 5, 2017
* Update bundler to avoid rubygems/bundler#3558 * Also Removing older Gemfile entries that fail travis
htanata
added a commit
to htanata/git_snip
that referenced
this issue
Oct 6, 2017
jamesbrauman
pushed a commit
to flippa/hexillion
that referenced
this issue
Oct 20, 2017
sriraamas
pushed a commit
to lucidsoftware/cumulus
that referenced
this issue
Oct 25, 2017
tachyons
added a commit
to tachyons/etcd-ruby
that referenced
this issue
Oct 29, 2017
See more details here rubygems/bundler#3558
tachyons
added a commit
to tachyons/etcd-ruby
that referenced
this issue
Oct 29, 2017
See more details here rubygems/bundler#3558
oleksandrbyk
added a commit
to oleksandrbyk/olek-ruby-wicked_pdf
that referenced
this issue
Feb 6, 2019
oleksandrbyk
added a commit
to oleksandrbyk/olek-elastic-rails
that referenced
this issue
Feb 6, 2019
Latest builds on Travis are broken because of bundler is too old and contains some issues See: rubygems/bundler#3558, travis-ci/travis-ci#3531 Related: #538
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
That exception occurs when running
bundle install
on the currentruby-head
...Have found this twice so far, and suspect I'll keep finding it if I keep looking:
The text was updated successfully, but these errors were encountered: