small medium large xlarge

Photo_on_2010-05-01_at_22.39_pragsmall
27 Apr 2010, 02:39
John H Simmonds (13 posts)

I fetched the source archive rails4-code.zip and tried to start the depot_t app. server using the new, simpler rails verb and got failure :

depot_t$ rails server –binding=10.25.183.83 –port=3003 Invalid application name server. Please give a name which does not match one of the reserved rails words.

Is the sample source compatible with Rails 3.0.0.beta3 ?

[I’m using Ubuntu linux 9.10 + Ruby 1.9.1p376]

Thanks!

Samr_small_pragsmall
27 Apr 2010, 09:44
Sam Ruby (634 posts)

Depot_t hasn’t been updated yet. Try depot_s.

Photo_on_2010-05-01_at_22.39_pragsmall
30 Apr 2010, 02:03
John H Simmonds (13 posts)

Thanks Sam.

Now I’m off to try Ruby 1.9.2 as the 1.9.1p378 VM crashes badly with Rails 3.0.0.beta3

I found a note about Ruby version compatibilities by chance .. is it worth a Topic here ?

Samr_small_pragsmall
30 Apr 2010, 12:03
Sam Ruby (634 posts)

While I am tracking it, I’m not sure I have anything productive to say just yet. The segfaults you see are intermittent. Rerun on the same machine without changing anything, and it just might work. I’ve seen 1.8.7, 1.8.8, 1.9.2, and 1.9.1 each crash with segfaults, and my perception of stability at the moment is in the order I just stated it (from most stable to least stable).

To the best of my ability, every example works on all four, and works with the latest version of Rails (checked out from git) and the latest version of 1.8.8 and 1.9.2 (checked out from svn and built from source). Put another way, if your goal is simply to learn Rails, and you are having a problem with any version of Ruby, switching to another version won’t inhibit you.

Samr_small_pragsmall
30 Apr 2010, 12:12
Sam Ruby (634 posts)

An example of a segmentation fault on 1.9.1. Note: that page is updated periodically, so while it shows a failure at the moment, it may not by the time you check on it.

Photo_on_2010-05-01_at_22.39_pragsmall
01 May 2010, 13:02
John H Simmonds (13 posts)

The Ruby 1.9.1 segfault behaviour I had is similar .. this version is way too unreliable for much meaningful Rails 3.0.0 exploration !

I’ll go back to 1.8.7 and hope for longer time between crashes, and fervently hope the Ruby core team are intrigued enough to fix the VM bug(s) soon ! (Rails is “just” Ruby code, isn’t it ?!)

Samr_small_pragsmall
01 May 2010, 15:55
Sam Ruby (634 posts)

As near as I can tell, that particular segfault has been fixed in Ruby 1.9.2. The current schedule for Ruby 1.9.2 was announced on March 15th, and projects for 1.9.2 to be ready in late July.

You must be logged in to comment