🦋 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.
jdv lizmat: thanks 01:45
06:15 lizmat_ joined 06:19 lizmat left
ab5tract jdv: removed 'Return '' instead of 0 when a uniprop is not found' from Fixes because it was reverted 07:12
07:45 finanalyst joined 07:47 lizmat_ left, lizmat joined
finanalyst lizmat: I compiled latest rakudo last night and its producing AST for numdefn and table that I was hoping for. thank you. 07:47
lizmat glad to hear! :-) 07:48
08:38 sena_kun joined 08:39 finanalyst left 10:36 raiph joined 10:44 finanalyst joined 12:07 finanalyst left 12:35 finanalyst joined 13:03 raiph left
jdv ab5tract: thanks. looks like i copied that to the ignore section with the revert but forgot the removing it from above:( 13:45
starting the releasings now
lizmat ++jdv 13:51
14:59 finanalyst left 15:12 vrurg_ left 15:24 vrurg joined
Geth rakudo/release-2024.05: 87afa6400a | (Justin DeVuyst)++ | 3 files
Update changelog + announcement

Deliberately not logged:
  [735fc4f3][aee3d259][05dcd081][741e6eaf][cdf127b1][f2a7e7d4]
  [10ee220a][48ef5c3e][539e4d26][b2684c07][0b3d180d][35c6c21b]
  [dc172ab5][2e05fe4d][5d6a7dfc][1fc67b1f][fa3c633d][cbc4f085]
  [1ace350e][c021e688]
15:36
16:44 finanalyst joined
ab5tract I always love it when I'm in the middle of writing out an explanation of behavior, then run the test case I'm going to use to demonstrate the behavior, only to subsequently discover that the output of the test case is the opposite of the behavior I expected :) 17:16
m: ({ say "this runs?" })() 17:17
camelia this runs?
ab5tract this is while writing an explanation about why `... where (* ~~ "this checks?")` doesn't check 17:18
maybe I'm just missing a layer of parens.. 17:19
m: ((*.say))("this says") # looks like that's not the case 17:20
camelia this says
jdv ab5tract: so what is the 6.c-errata change for your usage change? 17:56
actually both c and d errata have failures cause of the main/usage changes 18:00
ab5tract ? 18:02
jdv roast - there are 2 branches 6.c-errata and 6.d-errata that need to pass before a release 18:03
they are both broken because of the main stuff and i'm having a hard time figuring it out
ab5tract Why would we run branches for old versions against changes that fix the broken parts of those versions? 18:04
I guess I was supposed to wrap the fixes in some 6.e guards?
Let me give it a shot locally so I cane be more helpful 18:05
jdv the test files have "use v6.c". i'm not entirely sure about the whole versioning thing. i'm not sure anyone is. 18:06
lizmat: got any ideas here?
lizmat actually, not right now... have every confidence ab5tract will be able to help
jdv as i understand it the roast branch 6.c should run clean when that branch was cut and 6.c-errata should run clean anytime after that when using v6.c 18:15
ab5tract I see the issue. 18:17
or at least, I think I do..
it's `t/spec/S06-other/main-usage.t` that is failing, right? 18:18
jdv looks like in c yes 18:19
in d i had another issue but i think main-usage, main, and main-refactored maybe failed 18:20
ab5tract jesus 18:21
jdv trying to pick stuff off... its probably the most annoying part of releasing. meh.
running d now - maybe i'll get a clearer picture in a few minutes 18:24
ab5tract yeah, I can imagine... 18:25
next time a blin issue is raised, I'll try to manually run against these branches to be less surprised .. while packing for vacation :_) 18:26
jdv gist.github.com/jdv/63cd582222437b...39c9690486 18:30
normally i'd just cherry pick and fix it up but i'm not sure what your change is about esp wrt lang versions so i thought i'd ask if you were around to expedite it 18:33
ab5tract well, it's certainly not an urgent set of fixes.. but they are indeed fixes.. 18:35
one changes the return code from 0 to 2 when USAGE is called 18:37
the other makes enums that (unwisely, perhaps) overshadow CORE types to work 18:39
Geth roast/6.c-errata: f76c917a30 | (Justin DeVuyst)++ | S02-types/int-uint.t
Untodo some passing todos
18:41
jdv the other passing todo in c and d is a flapper which is more fun than i'm touching 18:42
ab5tract go ahead and revert the main stuff, it's more than I have the headspace for at the moment
jdv nah, its not that bad:) i'll try to butcher roast well enough. 18:43
thanks for the try.
Geth roast/6.c-errata: ad49a14d47 | (Justin DeVuyst)++ | S06-other/main-usage.t
Adjust to "return 2 when USAGE is called"
18:50
ugexe that is_run seems to be quite a bit behind the is-run in rakudo. the former tests status whereas the later tests exitcode 19:20
Geth roast/6.d-errata: 59e05b2048 | (Justin DeVuyst)++ | 3 files
Adjust to "return 2 when USAGE is called"
19:25
19:26 raiph joined
jdv ab5tract: all "fixed up" 19:38
ab5tract cheers! 19:39
lizmat jdv++ ab5tract++
.oO( a holiday well earned! )
ab5tract like I said earlier, I'll try to get in front of this a bit ahead of time next go round
jdv holiday sounds good 19:41
lizmat: there's a flapping todo test in at least 6.c-errata and 6.d-errata (not sure about master) and there's a test that stalls out in 6.d-errata but that only seems to happen when test test suite is run with a higher TEST_JOBS. should i file a bug on rakudo or on roast or something else? 19:49
lizmat yeah, data points are always good 19:51
on rakudo I'dsay 19:52
jdv ok
Geth nqp/main: 60229df932 | (Justin DeVuyst)++ | tools/templates/MOAR_REVISION
[release] Bump MoarVM revision to 2024.05
19:59
nqp/main: a534e01409 | (Justin DeVuyst)++ | VERSION
[release] Bump VERSION to 2024.05
rakudo/release-2024.05: ec3d5a5559 | (Justin DeVuyst)++ | tools/templates/NQP_REVISION
[release] Bump NQP revision to 2024.05
rakudo/release-2024.05: 509335d828 | (Justin DeVuyst)++ | VERSION
[release] Bump VERSION to 2024.05
rakudo: jdv++ created pull request #5585:
Release 2024.05
20:03
rakudo/main: 4 commits pushed by (Justin DeVuyst)++ 20:04
lizmat whee! jdv++
jdv patrickb: the may release happened 20:30
.tell El_Che the may release happened
tellable6 jdv, I'll pass your message to El_Che
jdv all done. have fun. later:) 20:31
21:02 finanalyst left
ab5tract jdv: sorry to bother you again, but is there an intermediate step required for the release to become available via the URLs in these pipelines? github.com/Raku/docker/pull/66 21:41
jdv i think that depends on rakudo star, right? 22:02
that's someone else. i'm just the root of the release tree so to speak 22:03
patrickb and El_Che do some and there are others that do others
anyone else remember who does rakudo star releases? 22:04
ab5tract: ^ 22:05
ab5tract ah, that makes (some) sense. I saw some connection to Rakudo Star but I assumed `Raku/docker` only depended on Raku releases 22:07
jdv it might be antonoks
yeah, its a decentralized fun time
well, kinda
ab5tract does the Rakudo release automatically update links and whatnot at rakudo.org? 22:08
jdv the source releases are all updated by me
so github, rakudo.org, and moarvm.org
ab5tract got it
Geth rakudo/main: 3f804996d9 | ab5tract++ | t/12-rakuast/xx-fixed-in-rakuast.rakutest
RakuAST: Add test case for stubbed packages defined withn parent package scope

This resolves R#4925 (#4925)
22:17
linkable6 R#4925 [open]: github.com/rakudo/rakudo/issues/4925 [Fixed in RakuAST] "Conflicted" namespaced stubs inside a class don't resolve
Geth rakudo/main: 9c53c92e79 | ab5tract++ | t/12-rakuast/xx-fixed-in-rakuast.rakutest
RakuAST: Fix plan
22:23 sena_kun left
Geth rakudo/coke/release-announce: 8b6d293615 | (Will Coleda)++ | tools/create-release-announcement.raku
Use inclusive TPF alias.
22:47
rakudo: coke++ created pull request #5586:
Use inclusive TPF alias.
22:48
rakudo/main: 271f83204b | (Will Coleda)++ (committed by ab5tract) | tools/create-release-announcement.raku
Use inclusive TPF alias.
23:01