🦋 Welcome to the IRC channel of the core developers of the Raku Programming Language (raku.org #rakulang). This channel is logged for the purpose of history keeping about its development | evalbot usage: 'm: say 3;' or /msg camelia m: ... | Logs available at irclogs.raku.org/raku-dev/live.html | For MoarVM see #moarvm
Set by lizmat on 8 June 2022.
00:07 reportable6 left 00:09 reportable6 joined 01:09 sourceable6 left, releasable6 left, linkable6 left, quotable6 left, tellable6 left, statisfiable6 left, greppable6 left, bloatable6 left, coverable6 left, evalable6 left, nativecallable6 left, reportable6 left, committable6 left, unicodable6 left, bisectable6 left, shareable6 left, benchable6 left, notable6 left, sourceable6 joined 01:10 bloatable6 joined, nativecallable6 joined, benchable6 joined, linkable6 joined, coverable6 joined, greppable6 joined, evalable6 joined, tellable6 joined 01:11 notable6 joined, reportable6 joined, shareable6 joined, quotable6 joined, unicodable6 joined 01:12 releasable6 joined, committable6 joined, bisectable6 joined, statisfiable6 joined 02:12 notable6 left, evalable6 left, coverable6 left, greppable6 left, quotable6 left, releasable6 left, shareable6 left, statisfiable6 left, sourceable6 left, benchable6 left, bloatable6 left, nativecallable6 left, tellable6 left, reportable6 left, bisectable6 left, committable6 left, linkable6 left, unicodable6 left, coverable6 joined 02:13 linkable6 joined, releasable6 joined, reportable6 joined, notable6 joined, tellable6 joined, bisectable6 joined, benchable6 joined 02:14 committable6 joined, unicodable6 joined, bloatable6 joined, statisfiable6 joined, sourceable6 joined, quotable6 joined, greppable6 joined, evalable6 joined, shareable6 joined 02:15 nativecallable6 joined 03:29 quotable6 left, sourceable6 left, coverable6 left, tellable6 left, benchable6 left, notable6 left, bisectable6 left, linkable6 left, bloatable6 left, statisfiable6 left, greppable6 left, shareable6 left, evalable6 left, committable6 left, nativecallable6 left, unicodable6 left, releasable6 left, reportable6 left, reportable6 joined, committable6 joined 03:30 bloatable6 joined, unicodable6 joined, notable6 joined, releasable6 joined, sourceable6 joined, bisectable6 joined, quotable6 joined 03:31 nativecallable6 joined, statisfiable6 joined, greppable6 joined, benchable6 joined, evalable6 joined, tellable6 joined, linkable6 joined, shareable6 joined 03:32 coverable6 joined 04:32 coverable6 left, evalable6 left, notable6 left, tellable6 left, bisectable6 left, greppable6 left, linkable6 left, bloatable6 left, committable6 left, statisfiable6 left, sourceable6 left, reportable6 left, nativecallable6 left, unicodable6 left, benchable6 left, shareable6 left, releasable6 left, quotable6 left, notable6 joined 04:33 statisfiable6 joined, benchable6 joined, unicodable6 joined, nativecallable6 joined, bisectable6 joined 04:34 evalable6 joined, reportable6 joined, shareable6 joined, linkable6 joined, tellable6 joined, greppable6 joined 04:35 sourceable6 joined, bloatable6 joined, quotable6 joined, committable6 joined, releasable6 joined, coverable6 joined 06:06 reportable6 left 06:07 reportable6 joined
Geth nqp: Kaiepi++ created pull request #776:
Make some enhancements to atomic integers
rakudo: Kaiepi++ created pull request #5000:
Make some enhancements to atomic integers
japhb Have been using idle time to work my way backwards on the Getopt::Long failure. Back as far as e7acf4930 it won't install. At 934f9895e, I get hangs trying to install an earlier module in my test list; I suspect fixing that was exactly was the e7acf4930 merge was *for*. 06:58
06:58 linkable6 left 06:59 linkable6 joined
japhb Looks like 5a8aa66bc was the last commit before one that was later reverted; checking there next (despite it being a bit of a jump back) 07:00
07:00 linkable6 left 07:02 linkable6 joined 07:16 djinni` left 07:29 djinni` joined
Geth JSON-Unmarshal: CIAvash++ created pull request #3:
Fix is unmarshalled-by trait issue
japhb Well 5a8aa66bc got *much* further in building things, but it hung testing Cro::HTTP, so that's a fail for a new reason 07:55
japhb tries 6dc2f92c9 in between 07:58
07:59 linkable6 left 08:01 linkable6 joined
japhb It being after 1 AM, I think I'm going to sleep while that builds (or attempts to, at least). See y'all in a few hours. :-) 08:04
08:52 sena_kun joined
Kaiepi LAPTOP-7I9RCT0C% raku --ll-exception -e 'say Counter(IntStr.new: 0, "ayy") ~~ Cool' 09:25
nqp can manage a *little* more than Any
takes a bit of convincing to do CALL-ME, though
09:29 discord-raku-bot left 09:30 discord-raku-bot joined 09:34 ab5tract joined, discord-raku-bot left, discord-raku-bot joined
Kaiepi oh, i can spare CALL-ME if i let hllization do its thing 10:15
nvm, i need it 10:19
Geth rakudo: 3d3966b0c4 | (Elizabeth Mattijsen)++ | src/core.c/Main.pm6
Fix lone "-" in MAIN handling with :named-anywhere

This resulted in an execution error:
   my %*SUB-MAIN-OPTS = :named-anywhere; sub MAIN(|) { }; @*ARGS = "-"
Without :named-anywhere, the lone "-" was already considered a positional argument.
JSON-Unmarshal/main: 1778fb8e0c | (Siavash Askari Nasr)++ (committed using GitHub Web editor) | lib/JSON/Unmarshal.rakumod
Fix is unmarshalled-by trait issue (#3)

Fixes #2
It seems putting `use JSON::Name` after `unit module` causes the issue.
11:23 evalable6 left 11:26 evalable6 joined 11:42 discord-raku-bot left 11:43 discord-raku-bot joined
lizmat m: sub MAIN(|c) { dd c }; @*ARGS = "--=" # this feels like an odd thing to allow ? 11:43
camelia \("" => IntStr.new(0, ""))
lizmat m: sub MAIN(|c) { dd c }; @*ARGS = "--=22" # this feels like an odd thing to allow ?
camelia \("" => IntStr.new(22, "22"))
11:48 discord-raku-bot left, discord-raku-bot joined 11:58 discord-raku-bot left, discord-raku-bot joined 12:07 reportable6 left 12:08 reportable6 joined
Geth rakudo: 31779f4701 | (Elizabeth Mattijsen)++ | src/core.c/DateTime.pm6
Add ACCEPTS method for DateTime

Fixes #5001
13:13 linkable6 left 13:15 linkable6 joined 13:34 ab5tract left 14:11 Xliff joined
Xliff P6-GLib suite timing statistics for Raku 2022.06.60.ga.7.e.9.b.1938 14:11
Total number of projects: 33 (483208 loc)
Total non-parallel compile times: 8905.310 (269.858 avg)
Total parallel compile times: 1505.717 (45.628 avg) 5.914x speedup
Still seeing an odd recompilation issue with one of my projects which is sucking an extra 100 seconds away from record timings. 14:12
15:50 vrurg_ joined, vrurg left 16:05 sena_kun left 16:07 ab5tract joined 16:09 sena_kun joined 17:20 sena_kun left 17:27 Kaiepi left 17:34 sena_kun joined 18:07 reportable6 left 18:09 reportable6 joined
japhb FINALLY: "Welcome to Rakudo™ v2022.06-33-g6dc2f92c9." 18:26
japhb inches forward to try 4fedb6f05 18:30
18:58 Kaiepi joined 18:59 dogbert11 joined, dogbert17 left
releasable6 Next release in ≈4 days and ≈23 hours. There are no known blockers. Please log your changes in the ChangeLog: github.com/rakudo/rakudo/wiki/ChangeLog-Draft 19:00
19:01 [Coke]_ joined 19:02 [Coke] left
japhb Hmmm, that one also hung on Cro::HTTP. I wonder if that's just a flaky test, or whether this range of Rakudo commits has a hang bug. 19:21
japhb retries on same version
19:29 [Coke]_ left 19:37 [Coke] joined 20:28 ab5tract left
japhb Yep, retry worked 20:28
OK, time to split Vadim's branch I think. Trying b4a26fbe4. 20:30
Boom, Getopt::Long fail. Closing in! 20:53
Same failure at 4ab617201. Time to try the last one: 7774c331c 21:08
21:17 sena_kun left
japhb Yup, that one fails too. 21:23
vrurg_: Looks like the Getopt::Long failures are caused by "7774c331c - Implement coercion via new-disp" (and not fixed by any later patches) 21:24
Don't know if that's a bug in the coercion changes or a fragility in Getopt::Long, but at least now you have a place to look .... 21:25
vrurg_ japhb: interesting as I use Getopt::Long pretty heavily in my work project. Any details? 21:35
21:35 vrurg_ is now known as vrurg
japhb vrurg: gist.github.com/japhb/fc7aea8417fd...8b5806cfe5 21:40
vrurg Interesting, does it mean I didn't reinstall it since the new-disp implementation? :) 21:44
japhb *chuckle* 21:45
vrurg I don't get the idea behind the test. What happens there? I don't use that feature of Getopt::Long and can't grok what is being tested. 21:49
japhb shrugs -- I just threw spare compute and disk space at narrowing down the failure introduction. I haven't actually looked at Getopt::Long itself. :-) 21:50
vrurg But it looks like it's a bug in the test. Seemingly, the option must produce a Foo, but parameter's type is Signature(Str). 21:51
Or Foo is cached by new-disp somehow because guards told it so... 21:56
jdv i think there's a bunch related to coercion 22:20
trying to curate the blin report atm 22:21
vrurg If I'm right (and I seem to be) the problem is likely to affect many cases. Will work on it today. 22:22
jdv looks like about 4 failures 22:27
vrurg: github.com/rakudo/rakudo/issues/5002 22:32
lizmat: the 2 at the top of that blin report look like they are related to changes of yours 22:33
did we ever address the issue that broke the ORM last release?
22:35 evalable6 left, linkable6 left 22:36 linkable6 joined, evalable6 joined 23:13 [Coke] left 23:15 [Coke] joined 23:26 melezhik joined 23:34 melezhik left