Installed the new “stable, recommended” version of Ruby as linked from ruby-lang.org, 1.8.7, and finding your Rails sessions breaking?
You’ll get an error like this:
/!\ FAILSAFE /!\ Tue Jun 10 15:09:34 -0500 2008 Status: 500 Internal Server Error wrong number of arguments (2 for 1) /usr/local/lib/ruby/1.8/cgi/session.rb:267:in `respond_to?'
This will be fixed in Ruby 1.8.7-2 but for now install this patch and restart the server.
I also had some enumerator errors, post a comment if you want a fix for that too.
Tags: ruby
June 13th, 2008 at 5:53 am
Thanks for the tip. I wasted several hours today trying to get two Rails apps to work (I gave up on the first one, installed the second, then ran into the same problem with that, too, which tipped me off.)
Shouldn’t this kind of thing be caught through testing before Ruby is released?
June 19th, 2008 at 7:41 pm
Thanks for the patch link.
I just reverted to Ruby 1.8.6 in the end!
June 19th, 2008 at 10:17 pm
David: Indeed, although an even more pertinent question might be “why are breaking, backwards-incompatible changes being introduced into the Ruby 1.8.x branch in the first place?”
Ric: Me too, as it happens. I fixed the first and second things, then when the third thing broke with no guarantee it wasn’t going to be a hundred more, I thought I’d revert and let the willing early adopter types work out all the issues before continuing…
June 22nd, 2008 at 12:30 pm
[...] people just can’t stop achieving! Not content with introducing breaking, backwards-incompatible changes into the Ruby 1.8 branch with 1.8.7, the Ruby Core team have shot for the moon, gone for gold, and doubled down all their bets – and [...]
June 26th, 2008 at 5:30 am
I’m new with Ruby, and I’m having this problem. Can you point out in a couple of words (or just put a link to some other place) on how to “install this patch and restart the server” ?
TIA
June 26th, 2008 at 10:32 am
Gaston,
If you’re new to Ruby you probably shouldn’t be patching it like this ; )
If you really want to keep Ruby 1.8.7, just export the latest version from svn and install that. It will have the change in this patch included – and recent security updates, too.
In fact the best thing to do is probably to download the latest 1.8.7 tarball from ruby-lang; they were forced to refresh them all recently because of the security problem, so they’re all nice and up to date. It’s really best to use the tarball versions so you know you have the exact same thing as everyone else.
December 5th, 2008 at 7:45 pm
Thanks for the tip
May 13th, 2009 at 11:37 pm
I found fix for this.
http://funonrails.wordpress.com/2009/05/13/fix-for-ruby-1-8-7-incompatibity/