Hi All,
Help!
How do I fix this?
# rpm -qa rakudo\*
rakudo-zef-0.1.30-1.fc27.x86_64
rakudo-0.2018.02.1-1.fc27.x86_64
# zef install Net::SMTP
===SORRY!===
Failed to open file
/usr/lib64/perl6/site/dist/863D6AAB4F5E7259BA381C4EBE0F88BAA358090E: No
such file or directory
# ls -al /usr/lib64/p
On Tue, 08 Aug 2017 04:19:24 -0700, elizabeth wrote:
> reverted c63c57e9a823303e74c06 for now
>
> > On 8 Aug 2017, at 12:21, Zoffix Znet (via RT) > follo...@perl.org> wrote:
> >
> > # New Ticket Created by Zoffix Znet
> > # Please include the string: [perl #131858]
> > # in the subject line of
OK, first of all, a bot-friendly (whateverable-friendly specifically) version
of the first snippet is here:
say run(:out, , ‘await ^100 .map: -> $i { start { "".match(/ { print
$i } /) } }’).out.slurp-rest eq (^100).join
And that points to the better-sched merge as noted by dogbert++
The second
On Wed, 09 Aug 2017 13:06:46 -0700, sml...@gmail.com wrote:
> This bug was found as a side-effect of RT #131870, but might be a
> separate issue:
>
> ➜ await ^10 .map: -> $i { start { "".match(/ { say $i } /) } }
> 7
> 7
> 6
> 6
> 7
> 8
> 9
> 9
>
On Wed, 09 Aug 2017 13:32:58 -0700, sml...@gmail.com wrote:
> Heh, on further thought, they may be the same issue after all.
>
> In `/(...) { ... $i ... $0 ... }`, both the $i and the $0 (or $/
> rather) are outer lexicals from the point of view of the curly block,
> right?
>
> So it might be a
Interestingly, I can't reproduce it as well… But the numbers are still higher
than they were, so I guess the ticket is valid?
Here's the output on all releases:
https://gist.github.com/Whateverable/8687cceb1bfcf39e9818cef819d29391
I'd say we can close it once we go back to 50-ish.
On 2017-08-17
dogbert++ noticed me that this ticket exist. I totally forgot.
OK, that particular leak is gone I think, but there were other (newer) issues.
See https://github.com/rakudo/rakudo/issues/1280
Closing this ticket in favor of GH issue.
On 2017-08-14 14:37:54, alex.jakime...@gmail.com wrote:
> OK, t
