🦋 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:54 guifa_ joined 00:55 guifa left
coleman Can anyone give me admin on examples repo? Need to set up CI. github.com/Raku/examples/pull/103 01:08
08:53 librasteve_ joined 08:54 lizmat left 08:55 lizmat joined
[Coke] looks like "NOC" group has admin 08:56
Geth rakudo/main: 10 commits pushed by (Stefan Seifert)++, (Daniel Green)++, MasterDuke17++
review: github.com/rakudo/rakudo/compare/9...bf909b7d53
08:58
[Coke] OOPS 09:00
Geth rakudo/main: 3dad1a55ae | (Stefan Seifert)++ | src/core.c/traits.rakumod
Revert "RakuAST: remove workaround needed by the old compiler frontend"

This reverts commit 617906054237bf1fe891f963a08d044c51e4c956.
The commit was merged accidentally and it breaks compilation with the old compiler frontend.
09:03
[Coke] jdv: that was an early merge of some rakuast stuff. The one reversion should mean we're OK for next release to not break anything, checking now 09:04
09:10 finanalyst joined
[Coke] coleman: we should consider using the same new build for doc-website for the examples site. 09:40
(and then we can treat examples like raku/doc as just content source) 09:41
(and start standardizing)
10:47 finanalyst_ joined 11:06 finanalyst left, finanalyst_ left, finanalyst joined 11:11 finanalyst left
nine The incompatible change most likely to cause ecosystem fallout is that Perl6::Metamodel::* is no longer available. It should always just have been Metamodel::* 11:22
greppable6: Perl6::Metamodel
greppable6 nine, 13 lines, 2 modules: gist.github.com/c5921031db32e3a178...6f971acba6
nine greppable6: NuT 11:23
greppable6 nine, 9 lines, 2 modules: gist.github.com/83eada619529e54460...a79b74ee20
13:26 socrates1298 joined
timo gist.github.com/timo/3c7c1fe695917...c02ff61130 lizmat, nine :) 14:50
jdv [Coke]: ok 14:56
15:12 socrates1298 left 15:28 vrurg left
timo updated my gist a few times 15:37
15:38 vrurg joined 18:37 lizmat left 18:39 lizmat joined
[Coke] is there a way I can tell zef is runnigng my tests? 19:15
japhb Are you wanting to know *from within the test* whether it is zef calling, or are you wanting to know *as the user of zef* whether your tests are being run correctly? 19:16
[Coke] from within the test. The functionaity in some cases is doing a git ls-files, which of course fails when you have a tarball that isn't a repo 19:17
japhb Ah gotcha.
Without touching the process tables, I don't know offhand, but I knew the clarification would be important for whomever could answer. :-) 19:18
nine Why not just check if there's a .git directory and maybe if it's actually one containing your code? 19:19
[Coke] I will probaby skip those tests for now unless some env var is set. (like for NETWORK_TESTING)
... or if no .git dir present, yes.
raku.land/zef:coke/RakuDoc::Test::Files is showing 0.3, but zef can't find it 19:46
(missing a zef update, bad timing) 19:47
timo i'm getting closer to a reproducible core.c.setting, i can feel it 22:13
(currently by throwing elements out without regard for what they were doing) 22:14
japhb
.oO( It turns out the empty buffer is very reproducible! )
22:26
timo lizmat: Breakpoint on SETTING::src/core.c/allomorphs.rakumod:338 hit by thread 1! / 1 Block <anon> SETTING::src/core.c/core_prologue.rakumod:79 22:41
it is indeed where we run val on environment variables going into our %*ENV hash
lizmat: gist.github.com/timo/76efafa7de1db...7f92ac8d07 22:45