I am running Rails 2.1.0 and ruby-1.8.6 (2008-06-20 patchlevel 230 [i686-linux]. I am experiencing the same segmentation faults that several others are who are running this version or ruby. Can anyone recommend a good workaround for these bugs until the Rails Core Team puts out something official?
On Tue, Jul 1, 2008 at 5:22 PM, liquid_rails <cheri.anacle...@gmail.com> wrote: > Hi,
> I am running Rails 2.1.0 and ruby-1.8.6 (2008-06-20 patchlevel 230 > [i686-linux]. I am experiencing the same segmentation faults that > several others are who are running this version or ruby. Can anyone > recommend a good workaround for these bugs until the Rails Core Team > puts out something official?
> Um, I somehow doubt it's Rails segfaulting. I'm running the same Ruby > and Rails and have had no issues.
> What exactly is throwing the seg faults?
> Jason
> On Tue, Jul 1, 2008 at 5:22 PM, liquid_rails <cheri.anacle...@gmail.com> wrote: > > Hi,
> > I am running Rails 2.1.0 and ruby-1.8.6 (2008-06-20 patchlevel 230 > > [i686-linux]. I am experiencing the same segmentation faults that > > several others are who are running this version or ruby. Can anyone > > recommend a good workaround for these bugs until the Rails Core Team > > puts out something official?
> On Jul 1, 2:25 pm, Jason Roelofs <jameskil...@gmail.com> wrote:
> > Um, I somehow doubt it's Rails segfaulting. I'm running the same Ruby > > and Rails and have had no issues.
> > What exactly is throwing the seg faults?
> > Jason
> > On Tue, Jul 1, 2008 at 5:22 PM, liquid_rails <cheri.anacle...@gmail.com> wrote: > > > Hi,
> > > I am running Rails 2.1.0 and ruby-1.8.6 (2008-06-20 patchlevel 230 > > > [i686-linux]. I am experiencing the same segmentation faults that > > > several others are who are running this version or ruby. Can anyone > > > recommend a good workaround for these bugs until the Rails Core Team > > > puts out something official?
> I am running Rails 2.1.0 and ruby-1.8.6 (2008-06-20 patchlevel 230 > [i686-linux]. I am experiencing the same segmentation faults that > several others are who are running this version or ruby. Can anyone > recommend a good workaround for these bugs until the Rails Core Team > puts out something official?
I'll probably get smacked for this, but you could certainly try JRuby in the meantime. We're not affected by those security issues and run Rails 2.1 fine...
From: Charles Oliver Nutter [mailto:charles.nut...@sun.com] # try JRuby in the meantime. We're not affected by those security # issues and run Rails 2.1 fine...
indeed. that's a great plus for jruby.
will jruby support ruby1.9 and future ruby versions?
Charles Oliver Nutter wrote: > I'll probably get smacked for this, but you could certainly try JRuby in > the meantime. We're not affected by those security issues and run Rails > 2.1 fine...
Possible roadblock: You're using native-code libraries that do not have JRuby analogues.
Peņa wrote: > From: Charles Oliver Nutter [mailto:charles.nut...@sun.com] > # try JRuby in the meantime. We're not affected by those security > # issues and run Rails 2.1 fine...
> indeed. that's a great plus for jruby. > will jruby support ruby1.9 and future ruby versions?
Yes, we plan to start adding 1.9 features over the summer and into fall, with final support being ready around 1.9.1 release time at Christmas.
From: Charles.O.Nut...@sun.com # Yes, we plan to start adding 1.9 features over the summer and # into fall, with final support being ready around 1.9.1 release # time at Christmas.
wow, very cool indeed.
i'd like to test it on ramaze since ramaze is 1.9 ready.
So a possibly vulnerable -p114 or a non-working -p230, nice.
Hmm, I didn't see problems locally because the ebuild for p230 includes a rollback patch that reverts change 15856. We'll see what the official fix is, hopefully it's soon.
On Wed, Jul 2, 2008 at 6:50 AM, Peņa, Botp <b...@delmonte-phil.com> wrote: > From: Charles.O.Nut...@sun.com > # Yes, we plan to start adding 1.9 features over the summer and > # into fall, with final support being ready around 1.9.1 release > # time at Christmas.
> wow, very cool indeed. > i'd like to test it on ramaze since ramaze is 1.9 ready.
Peņa wrote: > From: Charles.O.Nut...@sun.com > # Yes, we plan to start adding 1.9 features over the summer and > # into fall, with final support being ready around 1.9.1 release > # time at Christmas.
> wow, very cool indeed. > i'd like to test it on ramaze since ramaze is 1.9 ready.
For what it's worth, JRuby will support both 1.8 and 1.9 in the same distribution:
➔ jruby -help Usage: jruby [switches] [--] [programfile] [arguments] -0[octal] specify record separator (, if no argument) -a autosplit mode with -n or -p (splits $_ into $F) .. --1.8 specify Ruby 1.8.x compatibility (default) --1.9 specify Ruby 1.9.x compatibility --version print the version
|
