Fixed with 3c9cfdba88287e23e0ced8 (and further refined by later commits),
tests needed.
> On 6 Sep 2017, at 15:38, jn...@jnthn.net via RT
> wrote:
>
> On Tue, 05 Sep 2017 09:11:19 -0700, allber...@gmail.com wrote:
>> On Tue, Sep 5, 2017 at 5:40 AM,
Fixed with 3c9cfdba88287e23e0ced8 (and further refined by later commits),
tests needed.
> On 6 Sep 2017, at 15:38, jn...@jnthn.net via RT
> wrote:
>
> On Tue, 05 Sep 2017 09:11:19 -0700, allber...@gmail.com wrote:
>> On Tue, Sep 5, 2017 at 5:40 AM,
> On 6 Sep 2017, at 15:38, jn...@jnthn.net via RT
> wrote:
> To recap the IRC discussion yesterday: no, we haven't had this so far (except
> for stdout/stderr), and have gotten away with it due to the lack of output
> buffering. At present, we can either choose
> On 6 Sep 2017, at 15:38, jn...@jnthn.net via RT
> wrote:
> To recap the IRC discussion yesterday: no, we haven't had this so far (except
> for stdout/stderr), and have gotten away with it due to the lack of output
> buffering. At present, we can either choose
On Tue, 05 Sep 2017 09:11:19 -0700, allber...@gmail.com wrote:
> On Tue, Sep 5, 2017 at 5:40 AM, jn...@jnthn.net via RT <
> perl6-bugs-follo...@perl.org> wrote:
>
> > Failing to close output handles has been clearly documented (and yes,
> > documented well before the recent buffering change) as
On Tue, 05 Sep 2017 09:11:19 -0700, allber...@gmail.com wrote:
> On Tue, Sep 5, 2017 at 5:40 AM, jn...@jnthn.net via RT <
> perl6-bugs-follo...@perl.org> wrote:
>
> > Failing to close output handles has been clearly documented (and yes,
> > documented well before the recent buffering change) as
“Will leave this ticket open a little longer for further comments/discussion,
but my intention is to reject it.”
Nope, that's not exactly a good sounding plan.
We'll run toaster and fix all modules that require fixing (or create
appropriate issues if fixing something turns out to be too hard).
On Tue, Sep 5, 2017 at 5:40 AM, jn...@jnthn.net via RT <
perl6-bugs-follo...@perl.org> wrote:
> Failing to close output handles has been clearly documented (and yes,
> documented well before the recent buffering change) as something that can
> cause data loss. Default output buffering just makes
On Tue, Sep 5, 2017 at 5:40 AM, jn...@jnthn.net via RT <
perl6-bugs-follo...@perl.org> wrote:
> Failing to close output handles has been clearly documented (and yes,
> documented well before the recent buffering change) as something that can
> cause data loss. Default output buffering just makes
On Tue, 05 Sep 2017 05:29:00 -0700, 1parr...@gmail.com wrote:
> Perl 5 programmers are used to being casual about closing file
> handles. Obviously, 6 requires a change of habits. A cultural shift,
> if that's not too pretentious a term. Perhaps it needs to be mentioned
> in large, friendly
On Tue, 05 Sep 2017 05:29:00 -0700, 1parr...@gmail.com wrote:
> Perl 5 programmers are used to being casual about closing file
> handles. Obviously, 6 requires a change of habits. A cultural shift,
> if that's not too pretentious a term. Perhaps it needs to be mentioned
> in large, friendly
Perl 5 programmers are used to being casual about closing file
handles. Obviously, 6 requires a change of habits. A cultural shift,
if that's not too pretentious a term. Perhaps it needs to be mentioned
in large, friendly letters somewhere in the documentation?
On 9/5/17, jn...@jnthn.net via RT
Perl 5 programmers are used to being casual about closing file
handles. Obviously, 6 requires a change of habits. A cultural shift,
if that's not too pretentious a term. Perhaps it needs to be mentioned
in large, friendly letters somewhere in the documentation?
On 9/5/17, jn...@jnthn.net via RT
On Tue, 05 Sep 2017 00:54:27 -0700, alex.jakime...@gmail.com wrote:
> <[Tux]> CSV tests started to fail
> <[Tux]> # at t/90_csv.t line 260
> <[Tux]> # expected: $[["1", "2", "3"], ["2", "a b", ""]]
> <[Tux]> # got: $[["1", "2", "3"],]
> <[Tux]> # Failed test 'AOH parse out'
>
>
> Bisectable
On Tue, 05 Sep 2017 00:54:27 -0700, alex.jakime...@gmail.com wrote:
> <[Tux]> CSV tests started to fail
> <[Tux]> # at t/90_csv.t line 260
> <[Tux]> # expected: $[["1", "2", "3"], ["2", "a b", ""]]
> <[Tux]> # got: $[["1", "2", "3"],]
> <[Tux]> # Failed test 'AOH parse out'
>
>
> Bisectable
The issue is likely in Text::CSV so it's not fully a rakudo bug.
However, we probably have a bunch of broken modules in the ecosystem because of
this. I guess we need a Toaster report and a bunch of PRs for missing .close
calls to fix everything…
On 2017-09-05 00:54:27, alex.jakime...@gmail.com
# New Ticket Created by Aleks-Daniel Jakimenko-Aleksejev
# Please include the string: [perl #132030]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=132030 >
<[Tux]> CSV tests started to fail
<[Tux]> # at t/90_csv.t line 260
17 matches
Mail list logo