JRuby

gem update_rubygems Fails on JRuby 1.5.3

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Critical Critical
  • Resolution: Fixed
  • Affects Version/s: JRuby 1.5.3
  • Fix Version/s: JRuby 1.6RC3
  • Component/s: Core Classes/Modules
  • Labels:
    None
  • Environment:
    Windows
    jruby 1.5.3 (ruby 1.8.7 patchlevel 249) (2010-09-28 7ca06d7)
    (Java HotSpot(TM) Client VM 1.6.0_22) [x86-java]

Description

Also reported as bug against RubyGems on RubyForge:

The latest RubyGems has problems installing. However will work with Ruby 1.8 and not with JRuby 1.5.3

See RubyForge bug for more details and example of command line output.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
will mason added a comment -

Hi,

Addition - This turns out to be quite serious because any gem operation can now hang windows command shell. And the JVM /jruby process can't be killed, you can't logout, and you can't restart. That means the only way out is to power-down.

As I see it I can only clobber jruby and reinstall it with the installation gem version. That will get attended to eventually I'm thinking.

I think the hang is probably a JRuby issue. But it is instigated by the rubygem incompatibility.

Show
will mason added a comment - Hi, Addition - This turns out to be quite serious because any gem operation can now hang windows command shell. And the JVM /jruby process can't be killed, you can't logout, and you can't restart. That means the only way out is to power-down. As I see it I can only clobber jruby and reinstall it with the installation gem version. That will get attended to eventually I'm thinking. I think the hang is probably a JRuby issue. But it is instigated by the rubygem incompatibility.
Hide
Permalink
Charles Oliver Nutter added a comment -

Ok, I've managed to reproduce the issue. I updated the RubyGems bug and JRUBY-5517 with my findings and fix.

The problems stem from RUBYOPT env var being set. If you clear it, the issues go away. The root cause is that for in-process child "ruby" commands we're still using the system env for RUBYOPT when we should be using the inherited env. That is fixed for JRUBY-5517.

I don't see us spinning a 1.5.7 release for this. My recommendations would be:

  • unset RUBYOPT before updating
  • use JRuby 1.6
  • do nothing; RubyGems 1.x in JRuby 1.5.6 works fine too.

I'm going to mark this fixed in 1.6 RC3, but as I say...unlikely to cause a 1.5.7 release to happen.

Show
Charles Oliver Nutter added a comment - Ok, I've managed to reproduce the issue. I updated the RubyGems bug and JRUBY-5517 with my findings and fix. The problems stem from RUBYOPT env var being set. If you clear it, the issues go away. The root cause is that for in-process child "ruby" commands we're still using the system env for RUBYOPT when we should be using the inherited env. That is fixed for JRUBY-5517 . I don't see us spinning a 1.5.7 release for this. My recommendations would be: unset RUBYOPT before updating use JRuby 1.6 do nothing; RubyGems 1.x in JRuby 1.5.6 works fine too. I'm going to mark this fixed in 1.6 RC3, but as I say...unlikely to cause a 1.5.7 release to happen.

People

  • Assignee:
    Charles Oliver Nutter
    Reporter:
    will mason
Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: