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.
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
Proc::Async STDIN isn't handled correctly for all apps #5985
Comments
From david@empireofgames.comI'm attempting to use Perl6 && Proc::Async to automate a series of tests For some applications, everything works perfectly, while others do not. SSH is one example. When using key-based logins everything works Screen is another example (I'm trying to use this because my $serial_proc = Proc::Async.new(:w, :r, "screen", "/dev/ttyUSB0", $serial_proc.stdout.tap(-> $v { say $v; }); my $promise = $serial_proc.start; await $promise; # Exits almost immediately, with "Must be connect to a terminal" being the In this case, I found a temporary workaround using (ironically) ssh, for my $serial_proc = Proc::Async.new(:w, :r, "ssh", Another application I need to use with this is a (JTAG) debug tool. An I can't claim that I fully understand what's going on here, but clearly |
From @zoffixznetSome comments on this ticket: https://irclog.perlgeek.de/perl6-dev/2017-01-17#i_13935065 And https://irclog.perlgeek.de/perl6-dev/2017-01-17#i_13936857 |
The RT System itself - Status changed from 'new' to 'open' |
From @geekosaurOn Wed, Jan 4, 2017 at 11:20 PM, David E. <perl6-bugs-followup@perl.org>
Strictly speaking, this is not a bug: the interface for these kinds of The portability concern also means that pty support likely does not belong -- |
From david@empireofgames.comIt sounds like the functionality here would be a low-priority feature In either case, the official documentation ( Providing methods to tap into STDIN and STDOUT of a launched application While it adds a lot of overhead, the "ssh -t -t" approach seems to be the On Tue, Jan 17, 2017 at 3:41 PM, Brandon Allbery via RT <
|
Migrated from rt.perl.org#130512 (status was 'open')
Searchable as RT130512$
The text was updated successfully, but these errors were encountered: