This project is archived and is in readonly mode.
Rails3 beta4 + Ruby 1.9
Reported by Greg Donald | June 10th, 2010 @ 02:51 PM
When I try rails console using Rails3 beta4 and Ruby 1.9.1-p378
I
cannot save a record:
rails console Loading development environment (Rails 3.0.0.beta4)
ruby-1.9.1-p378 > g = Game.new
=> #
ruby-1.9.1-p378 > g.save
NameError: undefined method<=>' for classActiveSupport::Multibyte::Chars'
I found on someone's blog that exact error message and it said
to use
1.9.2-head, know issue, etc. So with 1.9.2-head I can't even
start
rails console:
rails console /Users/destiney/.rvm/gems/ruby-1.9.2-head/gems/railties-3.0.0.beta4/lib/rails/engine.rb:122:in
delegate': wrong argument type Symbol (expected Proc) (TypeError)
Comments and changes to this ticket
-
-
Julien Palmas June 10th, 2010 @ 03:57 PM
Got the same problem, using ruby-1.9.1-p378
This code has been introduced in 0042f4166f783085eb909d69d542b5323d8af5d6
and later changed only for Ruby 1.9 in 8d576b51a12fdb19e3993f3678ec64b2ea60fadaI'm going to contact Wycats to get more info
-
Micke Lisinge June 10th, 2010 @ 04:02 PM
I recently submitted a ticket with another problem with Activesupport::Multibyte::Chars
But i experience Greg's error first but it works after just a browser refresh but then the error in my ticket shows up right after the refresh.So to conclude:
- I get Gregs error explained here.
- I refresh my browser but then i get the error i report in my ticket (#4823)
My ticket is #4823
- I get Gregs error explained here.
-
DHH June 10th, 2010 @ 05:01 PM
- Assigned user set to “Yehuda Katz (wycats)”
-
José Valim June 10th, 2010 @ 06:55 PM
- State changed from “new” to “wontfix”
Rails does not support Ruby 1.9.1. Try using Ruby 1.9.2-preview3 (the latest preview) and you should be fine.
-
Greg Donald June 10th, 2010 @ 09:56 PM
Ruby 1.9.2-preview3 has the issue as well.
rails console /Users/destiney/.rvm/gems/ruby-1.9.2-preview3/gems/railties-3.0.0.beta4/lib/rails/engine.rb:122:in
delegate': wrong argument type Symbol (expected Proc) (TypeError) -
John McAliley June 22nd, 2010 @ 09:53 PM
- Assigned user cleared.
Greg,
Are you upgrading an app or was this from a new app generated with "rails new myapp"? I was getting the same error when I started the console on an app that I was trying to upgrade from 2.3. After I saw this error, I realized that I needed to upgrade additional parts of my app.. aside from what the rails_upgrade gem suggested. I updated several files, so I can't tell you exactly what fixed this, but the error went away after that. So if you are on the upgrade path, then generate a new app and compare the files with the app you are upgrading.I updated the following files:
/myapp/config/boot.rb /myapp/config/environment.rb /myapp/config/environments/*.rb /myapp/Rakefile- added: /myapp/config.ru
- added: /myapp/script/rails
- removed files from /myapp/script/
-
-
hiroshi July 6th, 2010 @ 04:41 AM
- Importance changed from “” to “Low”
FYI: This issue seems to be fixed by the commit:
http://github.com/rails/rails/commit/cfc9439454988a07451a7e26137956... -
-
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
<h2 style="font-size: 14px">Tickets have moved to Github</h2>
The new ticket tracker is available at <a href="https://github.com/rails/rails/issues">https://github.com/rails/rails/issues</a>
DHH
Greg Donald
Jeremy Kemper
José Valim
Julien Palmas
rbudiharso
Yehuda Katz (wycats)