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
unknown system error 0 via Proc::Async #5802
Comments
From @gfldexuse v6; CATCH { default { say .^name; say .Str } } my $find = Proc::Async.new(|<find / -print>); react { whenever $find.stderr(:bin) -> $line { $find.start; # OUTPUT (after some time): |
From @timoThe issue is that libuv will under some circumstances call the read The Solution™ is either to not call async_read at all when nread is 0, |
The RT System itself - Status changed from 'new' to 'open' |
From @jnthnOn Tue, 15 Nov 2016 09:46:14 -0800, timo wrote:
Or, even easier, to just change the incorrect `nread > 0` check to an `nread >= 0` check, which is what I've done in MoarVM commit 20e968b. Remaining question is if/how we should test this, short of just taking the code in here, adding a platform check for places that have a `find` command, and shoving it in as a stress test. Thoughts welcome. |
From @zoffixznetOn Wed, 16 Nov 2016 07:49:26 -0800, jnthn@jnthn.net wrote:
Committed a concoction that reliably exercises the bug ~90% of the time and runs fast enough on HEAD: Raku/roast@bc8b66866b |
@zoffixznet - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#130107 (status was 'resolved')
Searchable as RT130107$
The text was updated successfully, but these errors were encountered: