Re: [perl #123515] Using for + Supply.list results in high CPU usage

2014-12-29 Thread Elizabeth Mattijsen
> On 29 Dec 2014, at 03:05, Rob Hoelz (via RT) > wrote: > > # New Ticket Created by Rob Hoelz > # Please include the string: [perl #123515] > # in the subject line of all future correspondence about this issue. > # https://rt.perl.org/Ticket/Display.html?id=123515 > > > > See the attached

Re: [perl #123515] Using for + Supply.list results in high CPU usage

2014-12-29 Thread Moritz Lenz
On 29.12.2014 13:44, Elizabeth Mattijsen wrote: On 29 Dec 2014, at 03:05, Rob Hoelz (via RT) wrote: # New Ticket Created by Rob Hoelz # Please include the string: [perl #12351] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=

Re: [perl #123497] AutoReply: p6doc does not work on OSX (Rakudo * 2014.09)

2014-12-29 Thread Gabor Szabo
The same happens with panda. If I try to run directly I get /Users/gabor/rakudo-star-2014.12.1/install/bin/panda: line 2: use: command not found /Users/gabor/rakudo-star-2014.12.1/install/bin/panda: line 3: use: command not found /Users/gabor/rakudo-star-2014.12.1/install/bin/panda: line 4: use:

[perl #123519] earliest { ... } uses busy waiting when used with more than one channel, drives CPU usage up to 100%

2014-12-29 Thread via RT
# New Ticket Created by Rob Hoelz # Please include the string: [perl #123519] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=123519 > See also https://rt.perl.org/Ticket/Display.html?id=123515

[perl #121622] my @a; @a[3] = 1; @a[]:k; # (advent-2013-day12.t) aborting on perl6-j

2014-12-29 Thread Will Coleda via RT
On Wed Apr 09 14:56:31 2014, david.warring wrote: > fudged for jvm in advent/2013-day12.t > > % my @a; @a[3] = 1; @a[]:k' > java.lang.NullPointerException > in method reify at gen/jvm/CORE.setting:7425 > in method reify at gen/jvm/CORE.setting:7402 > in method reify at gen/jvm/CORE.setting:7

[perl #122342] Cannot call .++ using >> on an @array

2014-12-29 Thread Christian Bartolomaeus via RT
This problem was fixed with commit https://github.com/rakudo/rakudo/commit/8154bd396a I unfudged the corresponding tests and added some more tests to S03-metaops/hyper.t with commit https://github.com/perl6/roast/commit/3f8907e3f4 I'm closing this ticket now.

Is this a strange regex bug in my code?

2014-12-29 Thread Gabor Szabo
I am puzzled by this. I have code like this: my @files = dir("$.source_dir").map({ $_.basename }); for @files -> $tmpl { if $tmpl !~~ m/\.txt$/ { debug("Skipping '$tmpl' it does not end with .txt"); next; } debug("Source file $tmpl"); } and

Re: Is this a strange regex bug in my code?

2014-12-29 Thread Gabor Szabo
Just to follow-up: The problem appears in https://github.com/szabgab/Perl6-Maven/commit/4346c96d63e97def55e789bbeebdbdaebe8b0b33 After that I have replaced the regex match with if substr($tmpl, *-4) ne '.txt' { that works correctly, but I'd still like to understand if the bug was in my code, or

Re: Is this a strange regex bug in my code?

2014-12-29 Thread Patrick R. Michaud
Out of curiosity, is the bug still present if you use /\.txt$/ instead of m/\.txt$/ ? At the moment it looks like a Rakudo bug to me, but I haven't been able to golf it further to be certain. Pm On Tue, Dec 30, 2014 at 09:11:52AM +0200, Gabor Szabo wrote: > Just to follow-up: > The problem a

Re: Is this a strange regex bug in my code?

2014-12-29 Thread Gabor Szabo
No. If I remove the leading m from the regex, then the bug is gone. Gabor On Tue, Dec 30, 2014 at 9:19 AM, Patrick R. Michaud wrote: > Out of curiosity, is the bug still present if you use /\.txt$/ instead of > m/\.txt$/ ? > > At the moment it looks like a Rakudo bug to me, but I haven't been ab

Re: Is this a strange regex bug in my code?

2014-12-29 Thread Patrick R. Michaud
I suspect it may be some weirdness with the way that $_ is being handled in smartmatching, then. I think there's a slight difference between $tmpl ~~ /regex/ and $tmpl ~~ m/regex/ The first one does the equivalent of /regex/.ACCEPTS($tmpl), which ends up matching $tmpl directly again