dalek p: 4550f68 | samcv++ | src/QRegex/P6Regex/Grammar.nqp:
Supply a warning for using \K and instead suggest <(

or )>
08:46
p: ef24205 | lizmat++ | src/QRegex/P6Regex/Grammar.nqp:
Merge pull request #329 from samcv/regexK

P6 Regex: Supply a warning for using \K and instead suggest <( or )>
[TuxCM] This is Rakudo version 2016.11-156-g0428b79af built on MoarVM version 2016.11-44-g8e24145d 09:18
csv-ip5xs 3.350
test 14.578
test-t 6.654
csv-parser 16.674
babydrop samcv: that's a fatal error FWIW :) 11:03
m: try '/\b/'.EVAL; say $!.^name
camelia rakudo-moar 0428b7: OUTPUT«X::Obsolete␤»
babydrop samcv: if you wanted to bump the nqp version in rakudo as well, to bring in your nqp change, just run `git describe` in the nqp repo and put the output into rakudo's tools/build/NQP_REVISION 11:23
timotimo i always call "git describe --tags" for some reason
i wonder if it's necessary
jnthn iirc, only if you want to include unannotated tags 11:24
timotimo i forgot the difference between those :)
babydrop I think it was once, when we had that parrot tag that interfered? But that was fixed after the release (I mean 2 releases later, since I that was when I messed up the nqp tag on release :"P)_
samcv babydrop, it was a fatal error before though, because unrecognized escape sequence
will do that
jnthn An annotated tag is ref => object => commit
An unannotated tag is ref => commit 11:25
So an annotated one can have a message
babydrop samcv: yeah, fatal error is good. I was actually prepared to argue that it should be fatal and not a warning when I just saw the title in the notification :)
samcv ah
jnthn For some reason they're preferred, even though the message is almost always totally worthless. :P
samcv warnings you mean?
jnthn samcv: If you're asking me, no I was talking about annotated tags in git :) 11:26
samcv oh ok
timotimo i see
jnthn git tag -a 2016.11 ...hmmm, what message? "2016.11 release" :) 11:27
timotimo put the complete release notes in :P 11:28
jnthn :P
timotimo (they can already be grabbed via some git incantation)
babydrop NeuralAnomaly: stats
NeuralAnomaly babydrop, [✘] Next release will be in 1 week and 2 days. Since last release, there are 51 new still-open tickets (48 unreviewed and 0 blockers) and 159 unreviewed commits. See perl6.fail/release/stats for details
babydrop AlexDaniel: lol... just a couple of days ago I recall there being just like... 36 tickets :P 11:29
jnthn Yowser, that's a lot of tickets :P
babydrop AlexDaniel did a lot of quality assurance bug finding.
jnthn :) 11:30
samcv ok cool PR done 11:36
dalek kudo/nom: ee14067 | samcv++ | tools/build/NQP_REVISION:
NQP bump: Add nice error message when using \K in regex and suggest

Using <( or )>
11:41
kudo/nom: a987242 | (Zoffix Znet)++ | tools/build/NQP_REVISION:
Merge pull request #940 from samcv/nqpbump

NQP bump: Add nice error message when using \K in regex and suggest
babydrop samcv++
samcv how often does camelia rebuild? just curious 11:42
does it do it on every push or on a timer?
jnthn Timer; I think every 30 mins
babydrop samcv: my observations suggest its a cron job set on every 30m 11:43
nine It's every 20 minutes at 8, 28 and 48 minutes past the hour. 12:37
Our ecosystem contains lots of broken modules :/ 12:44
moritz I'd remove those that remain broken for quite some time (like, if there are open issues about the module not working at all for more than 6 months, or so) 12:47
babydrop wouldn't 13:05
If someone needing the module shows up, it'd be much easier for them to fix a fork than to start from scratch.,
huggable: camelia :is: Camelia updates every 20m at 8, 28, and 48 minutes of the hour 13:06
huggable babydrop, Added camelia as Camelia updates every 20m at 8, 28, and 48 minutes of the hour
[Coke] instead of removing them, having it tied to test results for modules would be awesomer. 13:08
lucasb whomever choose the minutes 8, 28 and 48 for building camelia, the OCD part of my brain wants to talk to you 13:22
moritz lucasb: why is that? 13:25
lucasb moritz: just a joke. personal preference for more round numbers 13:27
moritz camelia used to build a lot more compiler projects (niecza, std, perlito, kp6, ...), and they all got different offsets in minutes
to minimize load, while maximizing the number of rebuilds for projects that changed often
lucasb moritz: ok, now that's a explanation. makes sense. past explains the present :)
moritz in fact there are still more rebuild jobs right now, it's just that nobody cares about them 13:28
dalek kudo/nom: 7532297 | Altai-man++ | src/core/Rakudo/Internals/VMBackedDecoder.pm:
Fixes #130291: rt.perl.org/Public/Bug/Display.html?id=130291

The comment is removed because of irclog.perlgeek.de/perl6/2016-12-07#i_13698178
13:49
kudo/nom: 0089a55 | Altai-man++ | src/core/Rakudo/Internals/VMBackedDecoder.pm:
Tabs->spaces indentation fix
synopsebot6 Link: rt.perl.org/rt3//Public/Bug/Displa...?id=130291
kudo/nom: 08ccbbb | (Zoffix Znet)++ | src/core/Rakudo/Internals/VMBackedDecoder.pm:
Merge pull request #941 from Altai-man/empty-emit-fix

58cdfd8 | Altai-man++ | src/core/Rakudo/Internals/VMBackedDecoder.pm: Simplification of LAST block
dogbert17_ clickbaits lizmat with rt.perl.org/Public/Bug/Display.html?id=130294 14:40
kudo/nom: 7511b43 | lizmat++ | src/core/Rakudo/Internals/VMBackedDecoder.pm:
Merge pull request #942 from Altai-man/empty-emit-fix

Simplification of LAST block
pyrimidine re: RT#125938, I checked this morning from latest rakudo master and I still see the error, will try a fresh checkout and blow away my local installation just in case 15:23
synopsebot6 Link: rt.perl.org/rt3//Public/Bug/Displa...?id=125938
babydrop pyrimidine: what do you mean by "error"? 15:24
pyrimidine 'Numeric overflow' 15:25
babydrop, rt.perl.org/Public/Bug/Display.htm...xn-1419535
nine Some testing the ecosystem is no fun when tests run into endless loops... 15:26
pyrimidine trying again with a clean install just to check
babydrop pyrimidine: the expected behaviour is a X::Numeric::Overflow exception is thrown.
nine s/Some/Smoke/
babydrop m: try '2**10000000000'.EVAL; say $!.^name
camelia rakudo-moar 08ccbb: OUTPUT«X::Numeric::Overflow␤»
pyrimidine babydrop: Ah, then it's working just fine :)
babydrop pyrimidine: That should produce the same on OSX 15:27
sweet \o/
pyrimidine double-checking, I have two macs (laptop and a work iMac), test was on the former, rerunning on the latter 15:28
babydrop, this look correct? Seems fine: gist.github.com/cjfields/eb4c65e96...feea90423b 15:31
babydrop yup. thanks
pyrimidine another ticket down! babydrop++
babydrop .ask stmuk_ so is `zef` now the installer being shipped with R*? I notice our REPL message still references panda; wondering if that should read zef now 15:32
yoleaux2 babydrop: I'll pass your message to stmuk_.
babydrop .tell stmuk_ the message is the "You may want to `panda install Readline` or `panda install Linenoise` or use rlwrap for a line editor"
yoleaux2 babydrop: I'll pass your message to stmuk_.
stmuk_ babydrop: the last release was panda .. there is a branch which uses zef which will probably be the next release 15:33
yoleaux2 15:32Z <babydrop> stmuk_: so is `zef` now the installer being shipped with R*? I notice our REPL message still references panda; wondering if that should read zef now
15:32Z <babydrop> stmuk_: the message is the "You may want to `panda install Readline` or `panda install Linenoise` or use rlwrap for a line editor"
babydrop cool
.tell Zoffix s/panda/zef/; in REPL message prior to next release
yoleaux2 babydrop: I'll pass your message to Zoffix.
lucasb this switch gets rid of panda or both will be shipped together? 15:34
stmuk_ github.com/rakudo/star/tree/zef
currently panda isn't on that branch at all but I will probably add it back
babydrop is +1 on removing it completely
stmuk_ maybe it should warn its going away in the next R* release 15:35
babydrop or include a dummy executable that when run says "yada yada use zef now"
stmuk_: that sounds good 15:36
pyrimidine nine: I'm seeing errors installing Inline::Perl5 from rakudo master; should I go ahead and post an issue for it? gist.github.com/cjfields/cff17fab3...9997991293 15:39
nine pyrimidine: see them, too :/ 15:41
definitely caused by some change in rakudo 15:43
pyrimidine: are you by any chance bored enough to bisect rakudo for the change that caused the breakage? 15:44
pyrimidine nine: I'll give it a go, but it might be running in the background while I'm doing other things 15:45
nine pyrimidine++
dogbert17_ nine: can I tempt you with gist.github.com/dogbert17/c88ee798...e4960e885b 15:49
nine dogbert17_: I've already had a look but I'm still baffled. Will need to get some quiet time to give it another go. Maybe I'll find that this weekend. 15:51
dogbert17_ ++nine, many thanks it's the only nativecall test file which is still giving problems, you fixed the rest some time ago 15:52
nine I probably left the hardest one till last ;) 15:53
Ok, guests arriving. I'm outta here...
pyrimidine Bisecting: 10 revisions left to test after this (roughly 4 steps) 16:23
[f367e4edc189e090b83e81d5314f18bc438ccd39] Fix MVMArray Error on .pick with negative numbers
nine: makes sense it would be very recent, should have it pretty soon 16:24
pyrimidi_ nine: looks like it may be a moarvm change 17:05
Bisecting: 0 revisions left to test after this (roughly 1 step) 17:06
[b2ac4e44d136fb118c395b6649bebc25688487ca] Bump to get latest MoarVM.
verifying
dalek ast: c96e321 | Altai-man++ | S17-procasync/basic.t:
A test for #130291 (#189)

  * A test for #130291
  * Change literal name to $*EXECUTABLE
17:27
synopsebot6 Link: rt.perl.org/rt3//Public/Bug/Displa...?id=130291
ast: dbcdea0 | (Zoffix Znet)++ | S17-procasync/basic.t:
No need to quote a variable
17:28
pyrimidi_ nine: confirmed, it's b2ac4e44 17:48
nine: github.com/rakudo/rakudo/commit/b2...25688487ca 17:49
pyrimidine .tell nine in case you miss this in the backlog: Inline::Perl5 broke with github.com/rakudo/rakudo/commit/b2...25688487ca 17:52
yoleaux2 pyrimidine: I'll pass your message to nine.
dalek kudo/nom: 8cb3e1b | (Zoffix Znet)++ | src/core/Any-iterable-methods.pm:
Fix .first on Numerics

The logic in the method uses `+self` to get number of elements in the list, however, `self` is not guaranteed to be a list and may be a Numeric type, in which case we get an incorrect number.
Fix by using `self.elems` instead.
Bug find: irclog.perlgeek.de/perl6/2016-12-08#i_13705826
19:20
timotimo kch kch kch
very good
dalek ast: f2b3bf4 | (Zoffix Znet)++ | S32-list/first.t:
Test .first works when called on Numerics

Bug find: irclog.perlgeek.de/perl6/2016-12-08#i_13705826 Rakudo fix: github.com/rakudo/rakudo/commit/8cb3e1be4a
19:21
babydrop oh damn github.com/rakudo/rakudo/commit/8f...07b483f3c5 19:34
There was a reason for that + :/
"
"ZoffixW++ for spotting" heh
geekosaur your alter egos apparently need to learn to talk to each other :p
timotimo was there no test committed back then? 19:35
babydrop I think I may have forgotten one +. I see 4 instances in lizmat's commit and only 3 in mine and the quoted code still works in mine 19:36
hm 19:37
Well, I don't see that 4th instance anymore. That code changed. 19:38
So I guess yey? :)
.ask lizmat would you double check this commit? github.com/rakudo/rakudo/commit/8cb3e1be4a233 it fixes the bug that 3.first: :end; fails, but now I see your earlier commit: github.com/rakudo/rakudo/commit/8fdaada43 but the quoted code still works with my change. 19:39
yoleaux2 babydrop: I'll pass your message to lizmat.
lizmat . 19:40
yoleaux2 19:39Z <babydrop> lizmat: would you double check this commit? github.com/rakudo/rakudo/commit/8cb3e1be4a233 it fixes the bug that 3.first: :end; fails, but now I see your earlier commit: github.com/rakudo/rakudo/commit/8fdaada43 but the quoted code still works with my change.
lizmat babydrop: I'm feeling a bit under the weather 19:42
both commits look ok to me?
babydrop lizmat: I also had another question about matcher-less .first(). The :k, :kv, :p adverbs don't work on it. I looked at it and don't see any sane way of adding them without slowing everything down, so should we just spec that call as not taking adverbs? The user can ascertain the index without the adverbs, since there's no matcher, so they're kinda useless anyway? 19:43
Oh, OK.
lizmat: well, get rest then :)
lizmat babydrop: why would adding those adverbs slow everything down? 19:44
babydrop lizmat: Well, not everything, just the matcher-less .first 19:45
OK, I can add the adverbs. It's just any time I make anything slower I have an image of you with a look of unapproval :P 19:46
disapproval :)
lizmat hehe
if you're using a matcherless first, you should probably be using a .head anyway 19:47
babydrop true
lizmat so, if you want to use :k or friends with it, then by all means
the overhead is what you want :-) 19:48
babydrop :)
lizmat if you don't want it, use .head
or .tail in the :end case
which is what first with :end and no other adverbs should do anyway 19:49
afk& 19:50
babydrop: re 8cb3e1be4a233e888b57 , that looks ok to me 19:51
really afk&
babydrop OK. Thanks for looking at it. 19:52
dalek kudo/nom: ababb24 | (Zoffix Znet)++ | src/core/Any-iterable-methods.pm:
Fix matcher-less .first not respecting its :k, :p, and :kv adverbs

The multi handling the matcher-less candidate does not check whether any adverbs were passed.
Fix by removing that candidate and assigning `True` default to a candidate with Mu matcher.
IRC: irclog.perlgeek.de/perl6-dev/2016-...i_13706306
20:21
ast: 57b0f8c | (Zoffix Znet)++ | S32-list/first.t:
Test all adverbs work on .first without a matcher

Rakudo fix: github.com/rakudo/rakudo/commit/ababb246a3
20:22
kudo/nom: 345f6a7 | (Zoffix Znet)++ | src/Perl6/Actions.nqp:
Fix sink statement prefix not exploding Failures

In the Actions it code-genned to call .eager. Not sure why (copy-pasta from the <eager> in code above?), but changing that to call .sink showed no stresstest failures.
Bug finding: irclog.perlgeek.de/perl6/2016-12-08#i_13706422
20:46
ast: 49595cb | (Zoffix Znet)++ | S04-exceptions/fail.t:
Test `sink` statement prefix explodes Failures

Bug finding: irclog.perlgeek.de/perl6/2016-12-08#i_13706422 Rakudo fix: github.com/rakudo/rakudo/commit/345f6a7146
20:47