Ruby 2.0.0 doesn't work (Was: Cannot spin up new node on Heroku) #772

Closed
mathias opened this Issue Aug 29, 2013 · 2 comments

Projects

None yet

2 participants

@mathias
Contributor
mathias commented Aug 29, 2013

Hey folks.

I'm trying to DIY my way through spinning up a new node on Heroku, since the docs haven't been written yet (#475).

This is the error I'm seeing in the Heroku logs when I attempt to hit the homepage:

Processing by StaticController#homepage as HTML
NoMethodError (undefined method `empty?' for nil:NilClass):


Completed 500 Internal Server Error in 33ms

(with timestamp data stripped off those lines for clarity) Note that there are not line numbers in this output.

The empty? that might be called from the homepage is in https://github.com/hotsh/rstat.us/blob/master/app/views/updates/_list.html.haml#L52
But putting a nil check around updates there does not make this go away.

I tried to reproduce the bug by pointing my local rails server at the production MongoHQ database & setting other ENV variables to emulate production (RAILS_ENV=production etc) but I was not able to reproduce the empty? error.

Help?

@carols10cents
Contributor

Oh fun times. I had the same issue you did, so in trying to isolate the differences I added

ruby '1.9.3'

to the Gemfile to tell heroku to use 1.9.3 since 2.0.0 is now the default heroku uses for new apps-- and I have a new node going on heroku now.

So I'm guessing you're running 1.9.3 locally?

I'm going to push that change to the gemfile and change this issue to be about ruby 2.0.0 compatibility.... bleh.

@mathias
Contributor
mathias commented Aug 29, 2013

that worked. thanks @carols10cents ! 🍰

@sohocoke sohocoke pushed a commit to sohocoke/rails-mongo-api-server that referenced this issue Jan 22, 2014
@carols10cents carols10cents Specify ruby 1.9.3 in the Gemfile.
Heroku now uses ruby 2.0.0 as the default, but we appear to have some compatibilty issues somewhere (see hotsh/rstat.us#772).

Heroku will use the ruby specified in the Gemfile, so this should make for a more seamless deploy experience until we fix the compatibility problem(s).
65f0f67
@carols10cents carols10cents added the bug label Sep 29, 2014
@carols10cents carols10cents referenced this issue Oct 8, 2014
Merged

Ruby 2 #819

@wilkie wilkie closed this in #819 Oct 8, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment