|
View:
New views
13 Messages
—
Rating Filter:
Alert me
|
|
|
JRuby 1.1.2 + You (bug nomination time)We plan on putting out a version of JRuby (1.1.2) some time between
now and RailsConf (I would like to see us do this a good week before it like May 23 or May 26 at latest). So are there any bug that are really important to you that we should look at? We plan on doing some major bug triage at the beginning of this week and it would be nice to know which ones to look at first. -Tom -- Blog: http://www.bloglines.com/blog/ThomasEEnebo Email: enebo@... , tom.enebo@... --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
|
|
Re: [jruby-user] JRuby 1.1.2 + You (bug nomination time)JRUBY-2265
On Sat, May 10, 2008 at 11:39 AM, Thomas E Enebo <tom.enebo@...> wrote: We plan on putting out a version of JRuby (1.1.2) some time between |
|
|
Re: Re: [jruby-user] JRuby 1.1.2 + You (bug nomination time)Hi Alex,
On Sat, May 10, 2008 at 6:59 PM, Alex Durgin <alex.h.durgin@...> wrote: > JRUBY-2265 > > http://jira.codehaus.org/browse/JRUBY-2265 Done! Also, there was a major update to BigDecimal in JRuby lately, mostly triggered by a huge amount of new ruby spec tests (and attempts to pass them all), and now we do pass them all: 47 files, 227 examples, 5271 expectations, 0 failures, 0 errors And now is a great time to submit new bugs/tests against BigDecimal, if you have some! :) Thanks, --Vladimir --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
|
|
Re: JRuby 1.1.2 + You (bug nomination time)http://jira.codehaus.org/browse/JRUBY-2418
This prevents the will_paginate Rails plugin, and therefore Hobo, from working in JRuby. I've submitted a unit test and patch to fix the issue. -- Steen 2008/5/10 Thomas E Enebo <tom.enebo@...>: > We plan on putting out a version of JRuby (1.1.2) some time between > now and RailsConf (I would like to see us do this a good week before > it like May 23 or May 26 at latest). > > So are there any bug that are really important to you that we should > look at? We plan on doing some major bug triage at the beginning of > this week and it would be nice to know which ones to look at first. > > -Tom > > -- > Blog: http://www.bloglines.com/blog/ThomasEEnebo > Email: enebo@... , tom.enebo@... > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
|
|
Re: [jruby-user] JRuby 1.1.2 + You (bug nomination time)At 11:39 AM -0500 5/10/08, Thomas E Enebo wrote:
>We plan on putting out a version of JRuby (1.1.2) some time between >now and RailsConf (I would like to see us do this a good week before >it like May 23 or May 26 at latest). > >So are there any bug that are really important to you that we should >look at? We plan on doing some major bug triage at the beginning of >this week and it would be nice to know which ones to look at first. > This one's pretty important to me: http://jira.codehaus.org/browse/JRUBY-2495 Requiring and using a Java library that ends up using a Thread Context classloader doesn't work. Here's the problem in a nutshell: I get classnotfound errors when I try and use a Java library from a JRuby program when the library tries to dynamically create classes that are only defined by class resources accessible to the JRuby class loader (example: XMLDecoder). The issue is caused because the libraries use a thread context classloader which in the current implementation is only available to the ancestors of the JRuby class loader. Lots more detail in the Jira report. --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
|
|
Re: JRuby 1.1.2 + You (bug nomination time)Applied, thanks!
Steen Lehmann wrote: > http://jira.codehaus.org/browse/JRUBY-2418 > > This prevents the will_paginate Rails plugin, and therefore Hobo, from > working in JRuby. > > I've submitted a unit test and patch to fix the issue. > > -- Steen > > 2008/5/10 Thomas E Enebo <tom.enebo@...>: >> We plan on putting out a version of JRuby (1.1.2) some time between >> now and RailsConf (I would like to see us do this a good week before >> it like May 23 or May 26 at latest). >> >> So are there any bug that are really important to you that we should >> look at? We plan on doing some major bug triage at the beginning of >> this week and it would be nice to know which ones to look at first. >> >> -Tom >> >> -- >> Blog: http://www.bloglines.com/blog/ThomasEEnebo >> Email: enebo@... , tom.enebo@... >> >> --------------------------------------------------------------------- >> To unsubscribe from this list, please visit: >> >> http://xircles.codehaus.org/manage_email >> >> >> > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
|
|
Re: JRuby 1.1.2 + You (bug nomination time)Thomas E Enebo wrote:
> We plan on putting out a version of JRuby (1.1.2) some time between > now and RailsConf (I would like to see us do this a good week before > it like May 23 or May 26 at latest). > > So are there any bug that are really important to you that we should > look at? We plan on doing some major bug triage at the beginning of > this week and it would be nice to know which ones to look at first. I would like to see: http://jira.codehaus.org/browse/JRUBY-2488 to be fixed. It is about readline issues. Seems small, but since many users spend in IRB a lot of time it is kind of annoying. Also it in turn applies to the debugger console, rails console, ... At least Ctrl-R (history search) and Ctrl-D would be quite nice to have fixed. m. --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
|
|
Re: JRuby 1.1.2 + You (bug nomination time)Hi Martin,
On Mon, May 12, 2008 at 7:37 PM, Martin Krauskopf <Martin.Krauskopf@...> wrote: > I would like to see: > > http://jira.codehaus.org/browse/JRUBY-2488 > > to be fixed. It is about readline issues. Seems small, but since many users > spend in IRB a lot of time it is kind of annoying. Also it in turn applies > to the debugger console, rails console, ... > At least Ctrl-R (history search) and Ctrl-D would be quite nice to have > fixed. Looks like this *never* worked before, at least down to JRuby 0.9 I tried. So, this is not a regression, but I agree that would be nice to have working. At least the history search. Thanks, --Vladimir --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
|
|
Re: JRuby 1.1.2 + You (bug nomination time)Vladimir Sizikov wrote:
> Hi Martin, > > On Mon, May 12, 2008 at 7:37 PM, Martin Krauskopf > <Martin.Krauskopf@...> wrote: >> I would like to see: >> >> http://jira.codehaus.org/browse/JRUBY-2488 >> >> to be fixed. It is about readline issues. Seems small, but since many users >> spend in IRB a lot of time it is kind of annoying. Also it in turn applies >> to the debugger console, rails console, ... >> At least Ctrl-R (history search) and Ctrl-D would be quite nice to have >> fixed. > > Looks like this *never* worked before, at least down to JRuby 0.9 I tried. > So, this is not a regression, but I agree that would be nice to have > working. At least the history search. Hi Vladimir. I did not say it's a regression (at least I think so :) ). But I've just started to use jirb and debugger console very often, so it started to be bigger problem for me. It's often the case that I switch back to irb (if interpreter-independent) just because of history, even if I'm already running 'jirb' in one terminal. Maybe I'm just too used to the history and alike feature from bash and others 'readline-tools'. So might have different priority for other users. Personal taste. m. --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
|
|
Re: JRuby 1.1.2 + You (bug nomination time)Hi Martin,
On Mon, May 12, 2008 at 8:36 PM, Martin Krauskopf <Martin.Krauskopf@...> wrote: > I did not say it's a regression (at least I think so :) ). Yeah, sorry. It was mostly a note to myself. I was hoping that this stuff was working some time in the past, that would mean that there is a chance to make it work again with minimal effort. Well, I looked into JLine sources and it turned out that this is not the case, the history search or delete-word things or ALT-keys are not implemented there. I'll probably try to come up with some patches for JLine sooner or later, since I miss the very same functionality too. But this is definitely not for JRuby 1.1.2 though. Thanks, --Vladimir --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
|
|
Re: [jruby-user] JRuby 1.1.2 + You (bug nomination time)Hi,
Another strong candidate: JRUBY-1639: Exception when stopping WEBrick running the new rails application I've seen this not only with webrick, but when running the rubyspecs (Control-C doesn't terminate the run, just prints the exception and continues), and recently with newer UnixServer rubyspec that hangs, and again Control-C can't break this. Thanks, --Vladimir On Sat, May 10, 2008 at 6:39 PM, Thomas E Enebo <tom.enebo@...> wrote: > We plan on putting out a version of JRuby (1.1.2) some time between > now and RailsConf (I would like to see us do this a good week before > it like May 23 or May 26 at latest). > > So are there any bug that are really important to you that we should > look at? We plan on doing some major bug triage at the beginning of > this week and it would be nice to know which ones to look at first. > > -Tom > > -- > Blog: http://www.bloglines.com/blog/ThomasEEnebo > Email: enebo@... , tom.enebo@... > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
|
|
Re: [jruby-user] JRuby 1.1.2 + You (bug nomination time)Ah, sorry. Disregard that!
The bug number is incorrect. And I can't find the issue I filed (maybe I was only thinking of filing it?) :) In short, the problem is that Control-C doesn't kill the spec runs, and I've seen it also with mongrel or webrick. All the Control-C does is: Exception in thread "SIGINT handler" org.jruby.exceptions.MainExitException: aborted I'll investigate a bit more and provide the proper issue for that. Thanks, --Vladimir On Wed, May 14, 2008 at 9:59 PM, Vladimir Sizikov <vsizikov@...> wrote: > Hi, > > Another strong candidate: > > JRUBY-1639: Exception when stopping WEBrick running the new rails application > > I've seen this not only with webrick, but when running the rubyspecs > (Control-C doesn't terminate the run, just prints the exception and > continues), and recently with newer UnixServer rubyspec that hangs, > and again Control-C can't break this. > > Thanks, > --Vladimir --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
|
|
Re: [jruby-user] JRuby 1.1.2 + You (bug nomination time)Hi,
OK, I've found the jira issue for this problem: JRUBY-2454: Regression: Control-C doesn't kill RubySpec test run And I can verify that running rails with mongrel can't be terminated by single Control-C. Thanks, --Vladimir On Wed, May 14, 2008 at 10:06 PM, Vladimir Sizikov <vsizikov@...> wrote: > Ah, sorry. Disregard that! > The bug number is incorrect. And I can't find the issue I filed (maybe > I was only thinking of filing it?) :) > > In short, the problem is that Control-C doesn't kill the spec runs, > and I've seen it also with mongrel or webrick. > All the Control-C does is: > > Exception in thread "SIGINT handler" > org.jruby.exceptions.MainExitException: aborted > > I'll investigate a bit more and provide the proper issue for that. > > Thanks, > --Vladimir --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
| Free embeddable forum powered by Nabble | Forum Help |