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's .write appears to exit when the process run doesn't exist #5415
Comments
From @MasterDuke17This works like it should: perl6 -e 'my $p; try {$p = Proc::Async.new("asdfcat", </path/to/file that This doesn't: perl6 -e 'my $p; try {$p = Proc::Async.new(:w, "asdfcat"); CATCH {die "in |
From @zoffixznetIt's actually not throwing anything. The .write just seems to exit: $ perl6 -e 'my $p = Proc::Async.new(:w, "fdadsfdsafsd"); my $prom = $p.start; say "BEFORE"; say $p.write: "meow".encode; say "AFTER"; say await $prom;' I've seen this bug examined on IRC, but I don't see a ticket for it. |
The RT System itself - Status changed from 'new' to 'open' |
From @geekosaurOn Sun, Jul 3, 2016 at 10:22 AM, Daniel Green <perl6-bugs-followup@perl.org>
zsh: exit 141 I think I'd call that expected behavior. -- |
From @jnthnOn Sun, 03 Jul 2016 07:22:09 -0700, ddgreen@gmail.com wrote:
Fixed and tested in S17-procasync/nonexistent.t. (The change is to default to ignoring SIGPIPE, since we error-check all operations anyway. Those who do want to exit on SIGPIPE can write `signal(SIGPIPE).tap: { exit 1 }` or so. |
@jnthn - Status changed from 'open' to 'resolved' |
From @geekosaurOn Wed, Mar 8, 2017 at 11:33 AM, jnthn@jnthn.net via RT <
Hm. I'm going to guess this will interact badly with use as part of a shell -- |
Migrated from rt.perl.org#128526 (status was 'resolved')
Searchable as RT128526$
The text was updated successfully, but these errors were encountered: