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
When reading from stdin, eof is not respected #6288
Comments
From @usev6Currently rakudo on JVM does not respect eof when reading from stdin. bartolin_ r: .say for lines() For further discussion see https://irclog.perlgeek.de/perl6-dev/2017-05-27#i_14645528 I've fudged some tests in roast that were hanging due to this problem Those changes should be reverted, once the problem is solved. |
From @usev6On Sun, 28 May 2017 13:09:18 -0700, bartolin@gmx.de wrote:
Some of the mentioned tests are passing again (unfudged with Raku/roast@9ba8d28315). Also S19-command-line/repl.t is enabled for the JVM backend again: rakudo/rakudo@90303c1e3e Unfortunately, there is still something wrong with some tests in S32-io/pipe.t (and maybe elsewhere). I think it could be caused by nqp::readfh on stdin only returning when eof is encountered or 0x100000 bytes are read: https://github.com/rakudo/rakudo/blob/90303c1e3ec9b9b5f6aaef50bed85b4a9ff6455f/src/core/IO/Handle.pm6#L280 |
@usev6 - Status changed from 'new' to 'open' |
If I'm not mistaken, the remaining problem has nothing to do with Since the main problem is fixed, I'm closing this old issue. |
Migrated from rt.perl.org#131393 (status was 'open')
Searchable as RT131393$
The text was updated successfully, but these errors were encountered: