Windows inherit STDIN tty? about childprocess HOT 11 CLOSED

Hmm, good question. I'll get my hands on a Windows VM and give it a shot.

Until then, you could try something like this and see what happens:

process.duplex = true
process.start
IO.copy_stream(STDIN, process.io.stdin) # if the child process exits, this will raise Errno::EPIPE
process.wait

from childprocess.

I tried that but that actually didn't do anything. It just hung. I even tried a case where the child exits right away (echo foo).

from childprocess.

I got an OKAY workaround. It doesn't work 100% but it doesn't crash, either: hashicorp/vagrant@77c309e~...2f49449

from childprocess.

I've pushed a branch that hopefully solves the problem. At least this code now behaves similarily on Unix and Windows (tested on Ruby 2.0.0p353 and Windows 8.1):

proc = ChildProcess.build("ruby", "-e", "p STDIN.tty?; IO.copy_stream(STDIN, STDOUT)")
proc.io.inherit!
proc.start
proc.wait

Can you try out the windows-inherit-stdin branch and report back? No special casing (i.e. duplex = true) of Windows should be necessary.

If it works for you I'll do a bit more testing and then push a release.

from childprocess.

Your example does indeed work, but for some reason Cygwin and SSH isn't seeing it still:

Pseudo-terminal will not be allocated because stdin is not a terminal.
      0 [main] ssh 24220 fhandler_base::dup: dup(some disk file) failed, handle 0, Win32 error 6
dup() in/out/err failed

But from the same environment if I do the ruby -e p STDIN.tty? to ChildProcess, it returns true. Woe! I'll try to investigate further. Perhaps it is a bug with Cygwin/SSH on Cygwin

from childprocess.

Oh! Just kidding, your example fails as well within the context of the Vagrant code, but works in my bundle console. Investigating.

from childprocess.

How do you bring Cygwin into the picture? Are you running Ruby from Cygwin as well, or just SSH?

from childprocess.

Sorry Cygwin isn't in the picture. Sorry I wasn't clear I think this actually is working. Im just verifying.

from childprocess.

It works! :) Closing.

from childprocess.

Actually, I should probably leave it open until you merge it.

from childprocess.

Great! Merged and released as 0.4.0.

from childprocess.