Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Open3.capture2e fails with "wrong exec option" #2766

Closed
myronmarston opened this issue Mar 27, 2015 · 3 comments
Closed

Open3.capture2e fails with "wrong exec option" #2766

myronmarston opened this issue Mar 27, 2015 · 3 comments
Labels
core JRuby 1.7.x
Milestone
JRuby 9.0.0.0.pre2

Comments

@myronmarston
Copy link 

➜ ruby -v
jruby 1.7.8 (1.9.3p392) 2013-11-14 0ce429e on Java HotSpot(TM) 64-Bit Server VM 1.6.0_65-b14-462-11M4609 [darwin-x86_64]
➜ ruby -ropen3 -e 'Open3.capture2e("hostname")'
file:/Users/myron/.rubies/jruby-1.7.8/lib/jruby.jar!/jruby/kernel19/process.rb:14 warning: unsupported spawn option: in
TypeError: wrong exec option: [:out, :err]
  _spawn_internal at org/jruby/RubyProcess.java:1067
            spawn at file:/Users/myron/.rubies/jruby-1.7.8/lib/jruby.jar!/jruby/kernel19/process.rb:13
            spawn at file:/Users/myron/.rubies/jruby-1.7.8/lib/jruby.jar!/jruby/kernel19/kernel.rb:29
        popen_run at /Users/myron/.rubies/jruby-1.7.8/lib/ruby/1.9/open3.rb:204
          popen2e at /Users/myron/.rubies/jruby-1.7.8/lib/ruby/1.9/open3.rb:199
        capture2e at /Users/myron/.rubies/jruby-1.7.8/lib/ruby/1.9/open3.rb:365
           (root) at -e:
@headius
Copy link
Member

headius commented Mar 29, 2015

Works as expected in JRuby 9000's reimplemented process spawning.

@headius headius closed this as completed Mar 29, 2015
@headius headius added this to the 9.0.0.0.pre2 milestone Mar 29, 2015
@myronmarston
Copy link
Author

Thanks, @headius -- it'll be nice to see these sorts of bugs fixed in JRuby 9K :).

At this point, are you no longer fixing non-critical bugs in JRuby 1.7.x? If so, I'll stop reporting them.

@kares
Copy link
Member

kares commented Mar 30, 2015

@myronmarston even if it's not fixed its valuable to know what does not (and maybe won't) work in 1.7.x
... I would vote for keep 'em coming, unless they have a very similar underlying cause of course :)

@jeremy jeremy mentioned this issue Sep 30, 2015
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
core JRuby 1.7.x
Projects
None yet
Milestone
JRuby 9.0.0.0.pre2
Development

No branches or pull requests
3 participants
@headius @kares @myronmarston