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@acm.org , tom.enebo@gmail.com --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
on 10.05.2008 18:39
on 10.05.2008 19:00
What about an all out blitz on Rails performance - you could take a week or a couple days really looking closely at Rails perf and making some fixes/enhancements? Would seem to align nicely with the timing. Mike Mike Herrick Program Manager, Collaborative Software Initiative mike@csinitiative.com 1 SW Columbia Street, Suite 640 Portland, Or 97258 http://www.csinitiative.com 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. > > -Tom > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
on 10.05.2008 22:53
I'd like to see this one fixed (http://jira.codehaus.org/browse/JRUBY-1638 ). On 10-May-08, at 10:39 AM, Thomas E Enebo wrote: > -- > Blog: http://www.bloglines.com/blog/ThomasEEnebo > Email: enebo@acm.org , tom.enebo@gmail.com > > --------------------------------------------------------------------- > 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
on 10.05.2008 23:04
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
on 11.05.2008 00:08
JRUBY-2491 http://jira.codehaus.org/browse/JRUBY-2491 Reading the umask via File.umask sets the umask to zero. Its not critical, but its a one line fix & has a unit test included. 2008/5/11 Thomas E Enebo <tom.enebo@gmail.com>: > -- > Blog: http://www.bloglines.com/blog/ThomasEEnebo > Email: enebo@acm.org , tom.enebo@gmail.com > > --------------------------------------------------------------------- > 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
on 11.05.2008 00:35
The JRuby 1.1 show stopper for me is 'set_table_name incorrectly parses the passed string when it contains the schema owner' - (http://jira.codehaus.org/browse/JRUBY-2404). In English that means I can't use JDBC to access database tables with a dot '.' in their names. Oracle databases (to which I only have read access) have gone away. Richard Forster Thomas E Enebo wrote: > > > -- View this message in context: http://www.nabble.com/JRuby-1.1.2-%2B-You-%28bug-nomination-time%29-tp17165184p17168252.html Sent from the JRuby - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
on 11.05.2008 09:11
I think the biggest thing complicating Rails performance work is that...we don't really have good benchmarks. Mike Herrick wrote: > Portland, Or 97258 >> this week and it would be nice to know which ones to look at first. >> >> -Tom >> > > --------------------------------------------------------------------- > 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
on 11.05.2008 09:22
Can you submit a .patch file against AR-JDBC trunk? Darcy Schultz wrote: >> So are there any bug that are really important to you that we should >> To unsubscribe from this list, please visit: > > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
on 11.05.2008 22:24
On Sun, May 11, 2008 at 12:07 AM, Wayne Meissner <wmeissner@gmail.com> wrote: > JRUBY-2491 http://jira.codehaus.org/browse/JRUBY-2491 > Done! Thanks for the patch and the regression test. :) Thanks, --Vladimir --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
on 11.05.2008 22:28
Tom,
As for me, I think the following issue is important to be fixed (we've
seen few reports about this, including duplicating bugs):
JRUBY-2247: Object#methods is incorrect in some cases
The bug has a proposed patch attached, but I haven't had a chance to
review it yet (and maybe Charlie would be better qualified to look at
it -- it is related to apt and annotations stuff).
Thanks,
--Vladimir
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
on 11.05.2008 23:10
On Sun, May 11, 2008 at 3:27 PM, Vladimir Sizikov <vsizikov@gmail.com> wrote: > Tom, > > As for me, I think the following issue is important to be fixed (we've > seen few reports about this, including duplicating bugs): > > JRUBY-2247: Object#methods is incorrect in some cases > > The bug has a proposed patch attached, but I haven't had a chance to > review it yet (and maybe Charlie would be better qualified to look at > it -- it is related to apt and annotations stuff). This bug also bothers me quite a bit. I am sure we can get it done. I can also review. -Tom -- Blog: http://www.bloglines.com/blog/ThomasEEnebo Email: enebo@acm.org , tom.enebo@gmail.com --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
on 12.05.2008 00:41
I created a patch file of Jesse Hu's changes from JRUBY-2404 (a duplicate of JRUBY-1638) as compared to TRUNK as of today. His changes included mine and a couple others that looked related. I created Tracker ticket #20078 on Rubyforge and attached the patch file (http://rubyforge.org/tracker/index.php?func=detail&aid=20078&group_id=2014&atid=7857 ). Hopefully that's what you were requesting (first patch for me). thanks, Darcy. On 11-May-08, at 1:21 AM, Charles Oliver Nutter wrote: >>> So are there any bug that are really important to you that we should >>> To unsubscribe from this list, please visit: > 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
on 12.05.2008 08:19
This patch can fix AR-JDBC-Oracle related JRUBY-2404<http://jira.codehaus.org/browse/JRUBY-2404>(a duplicate of JRUBY-1638) and JRUBY-2463<http://jira.codehaus.org/browse/JRUBY-2463>as well. Thanks. 2008/5/12 Darcy Schultz <schuldar@gmail.com>:
on 12.05.2008 17:05
> 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. My team has some tests commented out because of this bug http://jira.codehaus.org/browse/JRUBY-2479. Basically, enough nesting of flow collections fails. We run into this because we use ActiveSupport::JSON.decode(@blah) in some of our tests [1]. An interesting aspect of the problem is that it fails under Java 1.5 but not Java 1.6. A possible fix is here http://code.google.com/p/jvyamlb/issues/detail?id=1 -- Matt [1] ActiveSupport::JSON.decode translates the JSON to YAML and then loads it. The JSON to YAML translation output flow mappings, at least for the JSON that our app is outputting. --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
on 15.05.2008 02:56
Richard Forster wrote: > The JRuby 1.1 show stopper for me is 'set_table_name incorrectly parses the > passed string when it contains the schema owner' - > (http://jira.codehaus.org/browse/JRUBY-2404). In English that means I can't > use JDBC to access database tables with a dot '.' in their names. Oracle > databases (to which I only have read access) have gone away. Nick took care of this. Another one down! - Charlie --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
on 15.05.2008 03:12
And as the submitter of the ticket, I really appreciate the fix! Not to mention all the effort you guys and gals are putting into this project in general; it's really great. Would it make sense to have some sort of auto update mechanism that ships with JRuby? Ever since 1.0 and the many releases within such a short period I always found myself extracting the latest built into a new directory, reinstalling my gems and once things are mirrored for the most part then I go ahead and change up my environmental variables. I don't know if this is the best method to go about doing an upgrade, feel free to point me to a better solution. I also realize this request isn't quite on topic with this thread so I apologize for the hi-jack. Take care and enjoy the trip to Japan, Charles! -MW On Wed, May 14, 2008 at 8:55 PM, Charles Oliver Nutter <charles.nutter@sun.com> wrote: > Nick took care of this. Another one down! > > - Charlie > > --------------------------------------------------------------------- > 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
on 15.05.2008 22:25
Hi Matthew, On Thu, May 15, 2008 at 3:11 AM, Matthew Williams <matthew.d.williams@gmail.com> wrote: > I don't know if this is the best method to go about doing an upgrade, > feel free to point me to a better solution. > > I also realize this request isn't quite on topic with this thread so I > apologize for the hi-jack. :) For me, the easiest and most convenient way is just to obtain JRuby from the sources and build it myself. That way, it's trivial to switch between the revisions, tags, versions via standard Subversion commands. (Well, using git-svn is probably even cooler, since switch between versions/revisions is, like, 0.1 sec!!!, very useful for regression hunting). :) Also, living off the sources from repository means that all the gems installed are just stay there and there is no need to re-install them over and over again. Thanks, --Vladimir --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
on 15.05.2008 23:31
Matthew Williams wrote: > Would it make sense to have some sort of auto update mechanism that > ships with JRuby? Ever since 1.0 and the many releases within such a > short period I always found myself extracting the latest built into a > new directory, reinstalling my gems and once things are mirrored for > the most part then I go ahead and change up my environmental > variables. > > I don't know if this is the best method to go about doing an upgrade, > feel free to point me to a better solution. We've moved our GEM_HOME out of the jruby dist. Our jruby upgrade process is to download, extract, check in, patch (so GEM_HOME is set), check in, and let everyone know where the new jruby is. Much less painful than reinstalling all the gems. Around line 40: if [ -z "$GEM_HOME" ] ; then GEM_HOME="${JRUBY_HOME}/../gems/1.8" fi inside the if $cygwin block, around line 158: GEM_HOME=`cygpath --mixed "$GEM_HOME"` right after the $cygwin block, around line 170: export GEM_HOME >> Richard Forster wrote: >> > > http://xircles.codehaus.org/manage_email > > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
on 16.05.2008 19:40
Matt Burke wrote: > > We've moved our GEM_HOME out of the jruby dist. Our jruby upgrade > process is to download, extract, check in, patch (so GEM_HOME is set), > check in, and let everyone know where the new jruby is. Much less > painful than reinstalling all the gems. This is probably the recommended way to handle frequent JRuby upgrades without reinstalling gems. We're blessed with the ability to have any number of totally isolated JRuby instances on a given machine, but when you don't want them totally isolated you need to do a bit more. I think it's ok this way though, and moving gem home out of the jruby install is pretty easy. - Charlie --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email