Redirect to IO.pipe on Windows causes inability to start a process about childprocess HOT 6 CLOSED

Hey @barancev, thanks for the report.

What you are trying to do is pretty straightforward, but this particular combination of tools (JRuby + Windows) is a little off the beaten path. Perhaps there are limitations with JRuby's implementation of IO.pipe that you're hitting in this context which don't play well with the process builder.

Would appreciate help from interested folks in investigating this particular issue. Thanks!

from childprocess.

Is it better to report this to the JRuby team?

from childprocess.

I would potentially open a bug with the JRuby team if you are unable to reproduce this bug on Windows with vanilla MRI Ruby.

The issue here is that we have code to use Windows-specific logic when running in JRuby on Windows, and I'm not sure how often this logic is exercised. The JRuby team may come back to say that it's an issue with the implementation.

If, however, you are able to get this to work with vanilla Ruby and not JRuby, that may suggest an issue with JRuby itself. Appreciate your help in investigating.

from childprocess.

Closing as there does not appear to be an effort to address. Happy to merge a pull request fixing the issue, if it is indeed specific to childprocess. Thanks!

from childprocess.

Sorry for silence, I've implemented a workaround and forgot about this issue...
Yes, it works with vanilla Ruby, so I'll report this issue to JRuby.

from childprocess.

Here it is: jruby/jruby#6102

from childprocess.