Zoffix m: say "abc" ~~ m:i/caaaaa/ 01:27
camelia ｢c｣
Zoffix pretty scary we don't have any tests catching something as basic as that :o 01:28
samcv timotimo, need a bit of help fixing this bug 01:30
m: say "b" ~~ m:i/ba/
camelia ｢b｣
samcv only on m:i and the last letter of left string batches the first of the right 01:31
m: say "aaaaaaaab" ~~ m:i/ba/
camelia ｢b｣
samcv and it doesn't happen with variables but only if it's actually written in the source code or EVAL'd 01:32
m: say "aaaaaaaaaaaaaaaaab" ~~ m:i/abaa/
camelia ｢ab｣
samcv m: say "aaaaaaaabcd" ~~ m:i/abcd111111/ 01:33
camelia ｢abcd｣
samcv m: say "aaaaaaaabcd" ~~ m:i/.abcd111111/
camelia ｢aabcd｣
samcv m: say "aaaaaaaabcd" ~~ m:i/3abcd111111/
camelia False
samcv hmm actually it's a problem in the moarvm function. ok 01:34
i know how to fix this then
probably.... 01:35
Zoffix Maybe we should knock it on the head and make Rakudo Star from 2017.05 instead of .04 02:10
Geth roast: 5401f288be | (Samantha McVey)++ | S05-modifier/ignorecase.t
Add tests for m:i bug

If the beginning of the needle matches towards the end of the haystack, it can return a partial match, when it hasn't traversed the needle fully. Add tests for this bug.		 04:51
samcv ok tests added. i have them passing in my build of mvm. will commit it in a bit
Geth nqp: ae6a610d84 | (Samantha McVey)++ | 2 files
Add tests for MVM indexic/equatic bug

Tests are todo until fix pushed to MVM.		 05:37
[Tux] This is Rakudo version 2017.04.2-22-g9ed89d947 built on MoarVM version 2017.04 06:41
csv-ip5xs 3.060
test 12.986
test-t 5.194 - 5.237
csv-parser 13.342
Geth nqp: 856d5c51a5 | (Samantha McVey)++ | tools/lib/NQP/Configure.pm
Enhance error reporting in Configure.pm when rev parse errors
 06:48
stmuk messages? 07:03
yoleaux 19 Apr 2017 18:31Z <Zoffix> stmuk: does R* have some sort of mechanism to apply patches or use non-release commit for release or something? The b4fa6d6792 fixes a REPL bug that affects REPL users on OSX who load Readline or Linenoise.
19 Apr 2017 22:38Z <Zoffix> stmuk: never mind. It's a much more minor issue than I originally thought. The history file just isn't saved between REPL runs and it displays a message about mkdir '/' 0o777 at startup. I also got a workaround that involves setting up an alias the users who really want their command line history: gist.github.com/zoffixznet/6a0d212...fa9efcc263
samcv ok i'm going crazy someone please help 07:13
see travis-ci.org/MoarVM/MoarVM/jobs/2...9074#L1062 07:14
i have no clue where this is coming from
tag 9999-please-do-not-use-these-7-gde3e5cf is bogus. but it seems to be trying to check it?
but it builds fine even on a clean checkout for me
hmm maybe i should clone more than depth 1 for nqp 07:15
stmuk .tell zoffix github.com/rakudo/star/tree/master/patches
yoleaux stmuk: I'll pass your message to zoffix.
samcv oh wait. nvm. i just pulled tags on mvm 07:16
and someone added a tag 9999-please-do-not-usethese
GREAT! and tags are not deletable!
nine WTF? 07:20
samcv i think we can probably ignore it though
hopefuly
rev =~ /(\d+)$sep(\d+)(?:$sep(\d+))?(?:-(\d+)-g[a-f0-9]*)?$/ 07:21
or die "Unrecognized revision specifier '$rev' $what\n";
is what we have in Configure.pm now
ok i'm getting the failure too now. i wasn't getting it on a clean install, but installed mvm to a branch new prefix and i hit the bug 07:23
stmuk .tell zoffix BTW I'm on holiday in Greece with poor connectivity so R* is likely to be delayed. I had problems with Grammar::Debugger but that's now fixed 07:26
yoleaux stmuk: I'll pass your message to zoffix.
samcv working on it right now...
nine samcv: we could also change MoarVM's Configure.pl to use git describe instead of git describe --tags 07:29
samcv oh 07:30
actually you're right
i'm looking in the wrong spot :)
i thought it was checking the moarvm repo tags or something
nine Yeah, because nqp's Configure.pl uses moarvm --version
err... moar --version
pushed 07:32
samcv yay 07:33
weird that that tag appeared 07:34
maybe timo accidently merged it in with telemeh 07:35
seems to work now
thanks nine 07:36
nine my pleasure :)
samcv now i can stop tearing my hair out 07:37
nine Yeah, first Travis builds passing 07:38
samcv i pushed it to my fork so i can check appveyor too 07:39
nine 0.16s$ perl Configure.pl --prefix=$MOAR_PREFIX --backends=moar; 07:50
Unknown option: backends
WTF?
travis-ci.org/MoarVM/MoarVM/jobs/224612634
samcv weird. idk why that's happening maybe the uh 07:51
readlink -f command words differently on mac? 07:52
i replaced `cd nqp` with `cd $NQP_FOLDER` which is done from readlink -f nqp # while in the moarvm folder
hmm stackoverflow.com/questions/105567...f-on-a-mac 07:54
lame-o
fixing now 08:01
there we go 08:19
that was more annoying that i thought it'd be at first. settled on 08:20
writing my own: resolve_folder () { O="$(pwd -P)"; D="$(dirname $1)"; T="$(basename $1)"; cd -- "$D" && cd -- "$T" && pwd -P; cd -- "$O" > /dev/null; }
since i don't need to resolve links or anything, and that should work for any normal folders
don't think i need quotes around VAR="$( )" though. yeah. i've learned if in doubt just quote everything :) 08:22
appears to be working now. good 08:33
still gotta fix the windows build though 08:54
bartolin lizmat: it looks like 3b0dec3255 does not work with the JVM backend :-/ 09:49
during stage parse it blows up with: Method 'X::TypeCheck::Binding::Parameter' not found for invocant of class 'QAST::SVal'
lizmat bartolin: does removing the BEGIN fix it? If so, maybe we should remove the BEGIN in case of the JVM ? 10:27
Zoffix .tell stmuk R* likely delayed you say... I'm thinking of maybe delaying it by 4 weeks and cutting it off 2017.05 or something isn't a bad idea. There are two pretty serious bugs in 2017.04.2 that we'd need to patch or point-release for 10:29
yoleaux 07:15Z <stmuk> Zoffix: github.com/rakudo/star/tree/master/patches
Zoffix: I'll pass your message to stmuk.
07:26Z <stmuk> Zoffix: BTW I'm on holiday in Greece with poor connectivity so R* is likely to be delayed. I had problems with Grammar::Debugger but that's now fixed
bartolin lizmat: I'll test (will take a while :-) 10:30
lizmat: looks good so far. I'm running a spectest and if that looks good as well, I'll add a special case for r-j (for the line with BEGIN only) 10:40
lizmat yeah, that's what I had in mind :-)
bartolin++
afk again& 10:41
jnthn Aha, my TPF grant report is posted: news.perlfoundation.org/2017/04/per...abi-3.html 10:54
yoleaux 21 Apr 2017 23:27Z <AlexDaniel> jnthn: fwiw irclog.perlgeek.de/perl6/2017-04-21#i_14466196
jnthn For anyone reading it and thinking "huh, did jnthn do those recently" - no, I wrote the grant report 2 months ago, it just took until now to be posted. :-) 10:55
Zoffix jnthn++ 10:58
Reliability definitely improved.
jnthn Glad it's felt by others :) 11:05
dogbert17 o/ 12:58
Zoffix: my apologies for disappearing during yesterdays TAP.pm6 debug session, someone at $work suggested that some beers should be consumed at a local pub and I fell for it 12:59
I have now run the spectest through gdb and here's what it looks like: gist.github.com/dogbert17/74e00499...f6d9769308 13:01
for those who didn't follow the discussion yesterday, the problem is that, if you run 'make spectest HARNESS_TYPE=6' with the default TEST_JOBS=1, then the process will run out of file handles if your system is set up to only have 1024 13:07
it seems as if one fd is lost for each test file being run and when you get to file ~1000 the spectest is aborted 13:08
hopefully the gist can give us a clue as to why 13:09
ZoffixMobile dog 14:33
Ugh 14:34
dogbert17: what perl6 version is that gdb for?
dogbert17 dogbert@dogbert-VirtualBox ~/repos/rakudo $ gdb -v 14:36
GNU gdb (Ubuntu 7.7.1-0ubuntu5~14.04.2) 7.7.1
the trick here is to break into the running perl6 process with 'sudo gdb -p <pid>', then you'll be able to set breakpoints an stuff 14:37
timotimo i think he meant perl6 --version 14:38
dogbert17 This is Rakudo version 2017.04.2-22-g9ed89d947 built on MoarVM version 2017.04
timotimo there's a config option somewhere in /sys or /proc that you can change so you can attach to your own processes
so you don't need to run gdb as root
dogbert17 aha
timotimo echo 0 > /proc/sys/kernel/yama/ptrace_scope 14:40
dogbert17 cool 14:42
github.com/rakudo/rakudo/blob/nom/...P.pm6#L885 14:45
timotimo nobody ever awaits the closing of the process? 14:47
like, $proc.out.lines(:close) or whatsit?
jnthn has a headache today, and figured he's share it by writing a blog post... 6guts.wordpress.com/2017/04/22/mas...ontention/
*he'd
lizmat jnthn++ 14:48
jnthn: also: s/dontate/donate/ 14:49
dogbert17 finds the code in TAP.pm6 quite hard to follow even without a headache
timotimo dotonate?
dogbert17 jnthn++ (blogging)
lizmat goes off and will read more when back
timotimo "mallocand friends" 14:50
Geth rakudo/nom: 624fe8fa2b | usev6++ | src/core/Exception.pm
[JVM] Don't initialize hash at compile time

The BEGIN phaser was added with 3b0dec3255, but doesn't work on JVM. It lead to an error during stage past: Method 'X::TypeCheck::Binding::Parameter' not found for invocant of class 'QAST::SVal'.		 14:56
timotimo good post 15:00
jnthn lizmat, timotimo: fixed those two, thanks 15:01
MasterDuke_ jnthn++, but "VM for a dyanmic language" 15:10
dogbert17 has trouble understanding "A given bin consists of:" 15:13
1 or more pages, each with space for a certain number of allocations of the bin size
MasterDuke_ also, "So, I belive" 15:14
timotimo dogbert17: well, there's one FSA, in it are multiple "size bins", where each bin holds objects of an upper and lower size limit 15:18
each of these "size bins" allocates pages full of slots of these sizes, i.e. it'll malloc 128 slots * 16 bytes
dogbert17 timotimo: thx 15:21
"When a thread termiantes," 15:40
Geth nqp: MasterDuke17++ created pull request #354:
Make profile sql output better		 15:54
MasterDuke_ timotimo, nine: if you care to check it out, github.com/perl6/nqp/pull/354 should enable the functionality you were asking for 15:56
timotimo sorry, i'm a half AFK 15:57
MasterDuke_ timotimo: i'm sorry, but this PR is going to expire in 10min unless you devote yourself to reviewing it. all the blame will rest on you 16:02
that's a reasonable expectation, right? 16:03
timotimo :) 16:04
yeah, i'll merge that 16:05
not quite a thorough code review, but since you've tested it and things give proper results, it's an improvement either way :) 16:06
MasterDuke_ well, might be good to have someone else test too
Geth nqp/master: 5 commits pushed by MasterDuke17++, timo++ 16:07
timotimo pff, testing
MasterDuke_ heh, but then again, i suspect i'm the only one who's ever used the sql profile output
timotimo i've just re-learned today that just committing stuff to master is totally fine
MasterDuke_ so even if it broke...
timotimo i've used it as if it were csv :P 16:08
i.e. not taken advantage of the structure and inter-table relations at all
or even joining a table with itself, as would be required with the call graph table
MasterDuke_ ah, still nice to know someone has used it
need to remember to correct the example in the docs when that hits rakudo 16:09
timotimo and now we should be in good shape to build a good tool for this
i didn't know this was docced :P
MasterDuke_ barely, docs.perl6.org/language/performanc...le_locally 16:10
timotimo i didn't even know! 16:11
is sqlite still in browsers for free?
MasterDuke_ but now you do, and that's half the battle
i think ff still uses it for some internal stuff, don't know otherwise 16:12
timotimo it might be time to remove "use of gather/take" from the performance page as a "performance weakness" 16:13
hmm.
if sqlite were still in browsers for free, we could host a static .html file on moarvm.org or rakudo.org or whatever and people would just pick their .sql file from disk and get all the data without it traveling over the network 16:14
MasterDuke_ that would be pretty cool
timotimo of course there's stuff like github.com/kripken/sql.js/
i wonder why its build is failing? 16:15
there is nothing in the travis build logs for the latest failed build 16:16
could it be it fell prey to the travis failure a few weeks back? 16:17
MasterDuke_ builds fine locally and passes `make m-test`
timotimo m-test? how come it has a moarvm backend?
MasterDuke_ i just specify it because sometimes i have a stray old jvm build lying around 16:18
timotimo i was refering to sql.js' build
MasterDuke_ ah, nm then 16:19
timotimo though you could just use the sql.js it offers and at least the demo page works 16:20
Clone done, sent: 1430 received: 25072049 ip: 67.18.92.124 16:24
server returned an error - clone aborted
?!? :(
could be because my version of fossil is ancient :P 16:27
MasterDuke_ fossil? 16:28
timotimo the SCM made and used by the sqlite folks
MasterDuke_ huh, never used it 16:29
timotimo it's slightly niche, but i hear great things about it 16:30
timotimo grabs an emscripten sdk 16:35
ugh, the makefile for sql.js is bogus 16:48
huh 16:52
how in the heck does this work
how does it know to put emcc in front ... 16:53
and now i have an up-to-date sql.js 16:54
now, do i even want to write this in html and js at all? 16:58
i didn't even consider that question :)
i have experience with python and qt, maybe i'll give that a shot, though maybe through Inline::Python rather than python directly 16:59
MasterDuke_ could the existing HTML be adapted to optionally the sql output? 17:00
timotimo probably
s: {a => 1}, "gist", \() 17:07
SourceBaby timotimo, Ehhh... I'm too scared to run that code.
timotimo s: Hash.new(), "gist", \() 17:08
SourceBaby timotimo, Sauce is at github.com/rakudo/rakudo/blob/624f...sh.pm#L213
samcv yawns- 17:22
too early
timotimo, if telemeh is not messing up the windows builds it's okay to bump nqp to get the m:i fix 17:23
timotimo well, i'm not saying it doesn't mess up the windows builds, but it does pass on appveyor 17:24
samcv .. 17:25
timotimo, mess up how?
timotimo i have no idea
samcv then how do you know it messes it up 17:26
timotimo it's windows, you know
and if it's windows ... you *know*.
samcv spectest passing
ok so you don't *know* but guess?
timotimo well, i know that being too confident is a bad idea when windows' involved :D
samcv yeah i guess 17:27
Zoffix \o/
Just got re-certified as Emergency Level C First Aid Responder :)
samcv well i'l be back in a few hours, going back to sleep for a bit. bump moar+nqp whenever you feel comfortable
timotimo cool
have a good sleep, samcv
samcv thank you :) 17:28
Zoffix Basically keeping you alive in any emergency long enough for ambulance to arrive... So... if you feel you're about to die. Ping me :P
samcv i feel i'm about to lose consiousness
timotimo oh
samcv zzzzzzzzzz
samcv &
timotimo i thought you meant C Programming Language First Aid Responder
Zoffix night
heh
samcv XD lol timotimo
we could use one of those too 17:29
timotimo yeah, i seem to find myself in need of that multiple times a month
YES! i have a terminal with sixel support \o/ 17:51
i think i'm going to bump nqp and rakudo now 18:46
huh 18:47
i have no idea by what mechanism my 9999-please-dont-use-these release causes Configure.pl to break in nqp 18:50
samcv: i'm going to remove what looks like left-over debug output, "long end 0 should-fail 0" 18:52
TimToady Zoffix: the problem with putting off R* even longer is that, the longer the cycle time on releases, the more pressure there is to sneak things in at the last moment because you know you won't get another chance for N months 18:58
so we should probably figure out how to move to a more continuous release process
TimToady is basically channeling obra++ here... 18:59
b2gills That was a big problem for Perl 5 until they went with a yearly release cycle 19:02
Geth nqp: f72fe4d04d | (Timo Paulssen)++ | 2 files
remove left-over debug output, bump moarvm for eqatic fix
 19:07
rakudo/nom: 7a3a6a8469 | (Timo Paulssen)++ | tools/build/NQP_REVISION
bump nqp for eqatic fix
rakudo/nom: version bump brought these changes: github.com/perl6/nqp/compare/2017....0-gf72fe4d
2bae61d69b | (Timo Paulssen)++ | lib/TAP.pm6

otherwise FDs will keep piling up and exhaust the system's ulimit of file descriptors. dogbert17++
Zoffix TimToady: seems apples and oranges to me. All I proposed is to base the next R* off 2017.05 Rakudo instead of making a 2017.04.3 point release or adding rakudo patches to R*. This doesn't affect the length of between future R* releases. 19:09
As for continuous releases... what is it? Releases more often than 1 month? Perl 6 VIP will be an end user release made monthyl, same day as Rakudo 19:11
TimToady no biggie, and I'm not a big fan of slippery slope arguments, but "Just This Once" tickles that neuron of mine :) 19:14
Zoffix I can always cut a new point release, if needed. Let me know 19:15
Zoffix & 19:16
dogbert17 oh, timotimo++ (bug crusher) 19:29
timotimo well, you pointed me at the exact location
dogbert17 I wouldn't have known what to do though :) 19:31
samcv yay got the merge 19:32
err bump
good *
timotimo was the debug output removal a good call? 19:33
samcv yeah that's fine
timotimo 'k
samcv from the .t file right
timotimo we should then un-todo some of these tests
samcv very yes
timotimo hm, is that in the roast or in nqp's test suite?
samcv both
timotimo t/moar/08-indexic.t (Wstat: 0 Tests: 117 Failed: 0) 19:34
TODO passed: 1, 92-105
yeah
samcv plus in roast too
timotimo i should have untodod that before bumping the version from rakudo's side
samcv yea 19:35
m: say 'abcd' ~~ /cdfg/
camelia Nil
samcv yay
timotimo there's a terminal emulator called "cancer" with the tagline "it's terminal" m)
samcv oh my 19:36
geekosaur oy 19:39
timotimo oy geekosaur 19:40
Geth nqp: cb60c0b32c | (Samantha McVey)++ | tools/lib/NQP/Configure.pm
Nicer debug output when git tags are confused
 19:41
nqp: 33aa810320 | (Samantha McVey)++ | t/moar/08-indexic.t
Untodo the now passing indexic tests
samcv looks like equatic still has the bug though 19:42
hmm
timotimo oh crap
samcv idk if we use equatic anywhere? 19:43
timotimo oh
i think my commit messages were all talking about eqatic
but only indexatic was fixed? 19:44
samcv yeah
timotimo dang
samcv yeah we don't use equatic anywhere
timotimo d'oh
samcv gonna look at it in mvm though. i though what i did would have fixed it but. lemme see
still not a release blocker though since it's not used anywhere 19:45
ok we use it in one place
m: say 'a' ~~ m:i/ab/ 19:46
camelia ｢a｣
samcv ok yeha need to fix this then
cause it does equatic first before doing an index i believe 19:47
at the very start of the haystack
m: say 'ba' ~~ m:i/ab/
camelia False
samcv ok this is EZ fix 19:49
yay i fixed it. will commit after i grab my tea 19:56
m: use nqp; say nqp::eqatic('st', 'sta', 0) 20:00
camelia 1
samcv m: use nqp; say nqp::eqatic('st', 'stassssssss', 0) 20:01
camelia 1
samcv m: use nqp; say nqp::eqatic('st', 'stassssssss', 0) 20:02
camelia 1
samcv gonna add a few more eqatic tests to nqp
to cover this bug better
pmurias (adding tests to nqp)++ 20:15
samcv ok added a few more tests, got some failures and further improved moar 20:34
after sitting down and drawing a ton of strings
running roast now 20:44
Geth nqp: 6a482c6ac9 | (Samantha McVey)++ | tools/build/MOAR_REVISION
Bump MoarVM for indexic and equatic fixes
 20:51
nqp: version bump brought these changes: github.com/MoarVM/MoarVM/compare/2...-gf0db8822
87501f7b08 | (Samantha McVey)++ | 2 files
¦ nqp: version bump brought these changes: github.com/MoarVM/MoarVM/compare/2...-gf0db8822
samcv we are a gooooo
robertle gooey? 20:55
Geth rakudo/nom: ce41e46602 | (Samantha McVey)++ | tools/build/NQP_REVISION
Bump MoarVM/NQP for case insensitive regex fixes
 20:56
¦ rakudo/nom: version bump brought these changes: github.com/perl6/nqp/compare/2017....-g87501f7b
samcv we are a GO
Geth roast: 7c72cadfcf | (Samantha McVey)++ | S05-modifier/ignorecase.t
Untodo now passing m:i tests
 20:58
samcv yay! 21:01
100% pass for equatic indexic and the m:i regex tests as well
Zoffix, let me know when you're around 22:13
and we can discuss another point release
AlexDaniel point release? 2017.04.3? \o/ 22:21
samcv idk. 22:22
yeah
anything
lizmat I got the impression we're going to not do any more point releases and have a Rakudo Star on 2017.05 ? 22:23
samcv hmm
idk the regex bug is bad
idk why were the only releases made
<samcv> m: say 'a' ~~ m:i/ab/
｢a｣
^
fixed now though
AlexDaniel c: releases say 'a' ~~ m:i/ab/ 22:24
committable6 AlexDaniel, ¦2015.12,2016.01.1,2016.02,2016.03,2016.04,2016.05,2016.06,2016.07.1,2016.08.1,2016.09,2016.10,2016.11,2016.12,2017.01,2017.02,HEAD(ce41e46): «False» ¦2017.03,2017.04.2: «｢a｣»
samcv oh nice AlexDaniel
AlexDaniel I'd say if it was there for more than two releases, it can wait for the next one 22:25
samcv hm
what were the other point releases for?
AlexDaniel not only we had the first *.2 release this time, you want it to be the first *.3 release also? :)
samcv i think the bug is severe enough to make another point release. suprised it wasn't found but 22:26
it could cause... issues
AlexDaniel yeah, yeah. Like any other bug actually 22:27
jnthn At this rate we'll be doing point releases up until the next pointless release. :P 22:33
samcv well. i mean not releasing a ponit release to fix a serious bug. seems not a good idea either 22:35
just because "we've had too many point releases"
timotimo every body wants a poni releaset 22:36
AlexDaniel bisect: o=2017.03 say 'a' ~~ m:i/ab/
bisectable6 AlexDaniel, On both starting points (old=2015.12 new=ce41e46) the exit code is 1 and the output is identical as well
AlexDaniel, gist.github.com/d362cb6c0d6bdecbab...dccb378c40
AlexDaniel meh…
not even sure how to use this bug 22:37
samcv how to use it?
AlexDaniel samcv: yea, bisectable is using :i in this case
samcv that code does trigger the bug
AlexDaniel I was trying to trigger it with o=2017.03
(should be old=2017.03)
but apparently that's not it
samcv oh it's new in 04 i think 22:38
bisect: o=2017.04 say 'a' ~~ m:i/ab/
bisectable6 samcv, On both starting points (old=2015.12 new=ce41e46) the exit code is 1 and the output is identical as well
samcv, gist.github.com/09c67862f09501b15f...8b57805734
jnthn I guess the counter-argument is that we fix things you could describe as serious in every release. 22:39
AlexDaniel samcv: no-no. Bisectable *itself* is running on a slightly older version
samcv oh
jnthn, well i think regressions are different than just normal fixes
jnthn I mean, most releases I've fixed some SEGV somewhere, even if by now they're getting harder and harder to hit upon
timotimo jnthn: i could benefit from you trying to compile a moarvm on your msvc; i've done a lot to please appveyor, but i can't know if it's enough until a Real Windows is let loose upon it
samcv point releases are useful for fixing regressions
AlexDaniel samcv: sometimes I hunt for regressinos using whateverable. There were times I submitted over 20 reports I think 22:40
and some of them were serious enough
samcv as serious as this?
MasterDuke_ what's the syntax for creating variable names with spaces in them? `my ::('a b') = 4` isn't it... 22:41
samcv NeuralAnomaly, status
NeuralAnomaly samcv, [✘] Next release will be in 3 weeks and 6 days. Since last release, there are 7 new still-open tickets (5 unreviewed and 0 blockers) and 43 unreviewed commits. See perl6.fail/release/stats for details
samcv 3 weeks is too long...
that's basically a month
timotimo are you sure a space is allowed with the special syntax?
m: my ::('$a b') = 4 22:42
camelia 5===SORRY!5=== Error while compiling <tmp>
Malformed my
at <tmp>:1
------> 3my ::('$a b')7⏏5 = 4
timotimo m: my ::('isthisit') = 4
camelia 5===SORRY!5=== Error while compiling <tmp>
Malformed my
at <tmp>:1
------> 3my ::('isthisit')7⏏5 = 4
AlexDaniel c: 2016.04,HEAD say (-∞^..^∞).in-range: 0/0
committable6 AlexDaniel, ¦2016.04: «True» ¦HEAD(ce41e46): «Value out of range. Is: <0/0>, should be in -Inf^..^Inf␤ in block <unit> at /tmp/f0scnurpLz line 1␤ «exit code = 1»»
MasterDuke_ pretty sure i saw TimToady do it
timotimo mhm
AlexDaniel c: 2016.07~50,HEAD say ().rotor(1) 22:44
committable6 AlexDaniel, ¦2016.07~50: «<anon|122856224>.new» ¦HEAD(ce41e46): «()»
timotimo whateverable helped fix a bunchton of json::fast stuff
AlexDaniel samcv: I dunno, some of these things don't look very good at all
samcv hm?
oh you saying bugs in releases? 22:45
were they regressions though?
AlexDaniel samcv: (re “as serious as this?”)
samcv: yes
samcv i think more people use regeex than rotor though
that's why i think it's more serious becuase perl is known for regex... 22:46
AlexDaniel but it is only with :i, and only relevant in some particular cases
samcv well.
there's tons of cases it can happen.
aaaaabc ~~ m:i/cd/ # also will fail 22:47
if the first character and last character match
AlexDaniel c: 2017.03,HEAD say ‘aaaaabc’ ~~ m:i/cd/
committable6 AlexDaniel, ¦2017.03,HEAD(ce41e46): «False»
samcv first char of the needle and last of the haystack
c: 2017.04,HEAD say ‘aaaaabc’ ~~ m:i/cd/ 22:48
committable6 samcv, ¦2017.04: «｢c｣» ¦HEAD(ce41e46): «False»
samcv soooo
that's not that specific
i mean somewhat specific. but uh. still too common.
timotimo we need to figure out fuzzing. 22:50
at a perl6 level, that is
AlexDaniel timotimo: well, I kinda have it figured out, in a way 22:51
timotimo: back in December/January I took all m: queries from the log and executed them on 2015.12, back then, HEAD 22:52
and this gave thousands of results that pointed out that everything has changed… 22:53
but that's how I found all these regressions
samcv nice
timotimo oooh
AlexDaniel that's a lot of manual work, but I have some plans on optimizing it 22:54
(maybe you can follow github.com/perl6/whateverable/issues/123 for updates on this, but this month I don't have much time to work on stuff anyway) 22:57
Zoffix: by the way, is it possible we don't remove [REGRESSION] tag from the title of bug reports even if they are resolved? 23:02
I'm not sure I understand the reason behind this. All I know is that it makes it harder for me to navigate through my reports
timotimo i wonder if we should try to fix the "but" + native parameter = invalid build_least_derived plan bug 23:10
it's probably just that the executor from the buildplan needs to have parts copied over to the build_least_derived one, but i think they've been different before and i have no idea why or in what way 23:11

Powered by Cro and the Raku® Programming Language.

Please report any issues / comments / feature requests as an issue on App::Raku::Log.

Thank you!