JRuby

File#directory? always returns false on Solaris

Details

  • Type: Bug Bug
  • Status: Resolved Resolved
  • Priority: Critical Critical
  • Resolution: Fixed
  • Affects Version/s: JRuby 1.6.6, JRuby 1.6.7
  • Fix Version/s: JRuby 1.7.0.pre2
  • Component/s: Core Classes/Modules
  • Labels:
  • Environment:
    OpenIndiana b151a x86_64
    OpenSolaris 2009.06 x86
  • Number of attachments :
    0

Description

I noticed strange error messages when trying to install any gem using RubyGems:

ERROR:  While executing gem ... (Errno::ENOENT)
    No such file or directory -

After doing some investigating I narrowed down the problem to File.directory?:

$ irb
irb(main):001:0> JRUBY_VERSION
=> "1.6.7"
irb(main):002:0> File.directory? '/'
=> false
irb(main):003:0> bklang@openindiana:~/jruby-1.6.7$ uname -a
SunOS openindiana 5.11 oi_151a i86pc i386 i86pc Solaris

I have verified this is an issue on Solaris, but NOT an issue on OS X. Also this is a regression, as the issue is not present in JRuby-1.6.5.1 and earlier:

$ irb
irb(main):001 > JRUBY_VERSION
 => "1.6.5.1" 
irb(main):002 > File.directory? "/"
 => true

Issue Links

is depended upon by

Improvement - An improvement or enhancement to an existing feature or task. SONAR-4046 JRuby error when launching the Sonar server on Solaris

  • Minor - Minor loss of function, or other problem where easy workaround is present.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Hiro Asari added a comment -

Does the problem persist with -Xnative.enabled=false?

Show
Hiro Asari added a comment - Does the problem persist with -Xnative.enabled=false ?
Hide
Permalink
Ben Klang added a comment -

That flag seems to fix it, yes:

$ export JRUBY_OPTS="--1.9 -Xnative.enabled=false"
$ irb
jruby-1.6.7 :001 > File.directory? '/'
=> true
jruby-1.6.7 :002 > File.directory? '/nonexistent'
=> false
jruby-1.6.7 :003 > File.directory? '/usr'
=> true

Show
Ben Klang added a comment - That flag seems to fix it, yes: $ export JRUBY_OPTS="--1.9 -Xnative.enabled=false" $ irb jruby-1.6.7 :001 > File.directory? '/' => true jruby-1.6.7 :002 > File.directory? '/nonexistent' => false jruby-1.6.7 :003 > File.directory? '/usr' => true
Hide
Permalink
Damian Monogue added a comment -

While it's true that -Xnative.enabled=false causes File.directory?() to report correctly, it should be noted that it does not seem to resolve the problem with installing rubygems. It wasn't until I moved to jruby 1.6.5.1 that I was able to run through the gem install.

Show
Damian Monogue added a comment - While it's true that -Xnative.enabled=false causes File.directory?() to report correctly, it should be noted that it does not seem to resolve the problem with installing rubygems. It wasn't until I moved to jruby 1.6.5.1 that I was able to run through the gem install.
Hide
Permalink
zipizap added a comment - - edited

It also happens on "SunOS 5.10 Generic_142900-03 sun4u sparc SUNW,Sun-Fire-V440"... reverting back to jruby 1.6.5.1 as suggested (and it works again)

Show
zipizap added a comment - - edited It also happens on "SunOS 5.10 Generic_142900-03 sun4u sparc SUNW,Sun-Fire-V440"... reverting back to jruby 1.6.5.1 as suggested (and it works again)
Hide
Permalink
Charles Oliver Nutter added a comment -

We need to do a pass over all native stuff on Solaris for any 1.7 final release.

Show
Charles Oliver Nutter added a comment - We need to do a pass over all native stuff on Solaris for any 1.7 final release.
Hide
Permalink
Neil Brennan added a comment -

This issue is pretty much a show-stopper for us with our Rails 3.2 upgrade.

We appear to be caught in a nasty dependency vortex. Rails 3.2 requires JRuby 1.6.6 or later, but JRuby 1.6.5 is the last version that can successfully install gems on Solaris.

Would love to see this resolved, as we are totally stuck.

Show
Neil Brennan added a comment - This issue is pretty much a show-stopper for us with our Rails 3.2 upgrade. We appear to be caught in a nasty dependency vortex. Rails 3.2 requires JRuby 1.6.6 or later, but JRuby 1.6.5 is the last version that can successfully install gems on Solaris. Would love to see this resolved, as we are totally stuck.
Hide
Permalink
Ben Summers added a comment -

I believe I have resolved this issue, see this github pull request:

https://github.com/jnr/jnr-posix/pull/9

Show
Ben Summers added a comment - I believe I have resolved this issue, see this github pull request: https://github.com/jnr/jnr-posix/pull/9
Hide
Permalink
Scott Severtson added a comment -

I can confirm that Ben Summers' solution resolves the File.directory? issue when applied to JRuby 1.6.7 on Solaris 10 x86.

I can also confirm that "-Xnative.enabled=false" workaround resolves the same issue, but introduces other problems due to some file operations not being implemented in non-native code.

Show
Scott Severtson added a comment - I can confirm that Ben Summers' solution resolves the File.directory? issue when applied to JRuby 1.6.7 on Solaris 10 x86. I can also confirm that "-Xnative.enabled=false" workaround resolves the same issue, but introduces other problems due to some file operations not being implemented in non-native code.
Hide
Permalink
Charles Oliver Nutter added a comment -

This should be resolved now in jnr-posix, but leaving this open to ensure we ship the latest jnr-posix with 1.7pre2.

Show
Charles Oliver Nutter added a comment - This should be resolved now in jnr-posix, but leaving this open to ensure we ship the latest jnr-posix with 1.7pre2.
Hide
Permalink
Charles Oliver Nutter added a comment -

Tom is in the process of updating jnr-posix, so I'm marking this resolved.

Show
Charles Oliver Nutter added a comment - Tom is in the process of updating jnr-posix, so I'm marking this resolved.
Hide
Permalink
Unic Man added a comment -

Can I know the GA date of 1.7. We also need to have Solaris support and we have just migrated to rails 3.2.x platform on rails 1.6.7 and our release is totally stuck due to this defect.

Show
Unic Man added a comment - Can I know the GA date of 1.7. We also need to have Solaris support and we have just migrated to rails 3.2.x platform on rails 1.6.7 and our release is totally stuck due to this defect.
Hide
Permalink
Thomas E Enebo added a comment -

Unic man, barring significant blocker we are looking at tomorrow (friday) or possibly Monday.

Show
Thomas E Enebo added a comment - Unic man, barring significant blocker we are looking at tomorrow (friday) or possibly Monday.

People

  • Assignee:
    Charles Oliver Nutter
    Reporter:
    Ben Klang
Vote (1)
Watch (9)

Dates

  • Created:
    Updated:
    Resolved: