🦋 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: ... | log inspection situation still under development | For MoarVM see #moarvm
Set by lizmat on 22 May 2021.
[Coke] I'm not a sparrow user - what's the spawned bash script doing (that's where the segfault is, yes) 00:44
melezhik .tell SmokeMachine hopefully I fixed SparkyCI performance and false negative issues , please try to run new builds for Red and let me know if you have any issue 02:24
tellable6 melezhik, I'll pass your message to SmokeMachine
melezhik the service is still in deep development, so things may happen ))) 02:25
releasable6 Next release in ≈1 day and ≈15 hours. 1 blocker. Please log your changes in the ChangeLog: github.com/rakudo/rakudo/wiki/ChangeLog-Draft 03:00
[Tux] Rakudo v2022.03-231-g522c5fc83 (v6.d) on MoarVM 2022.03-17-g794e1d589
csv-ip5xs0.788 - 0.791
csv-ip5xs-204.948 - 5.241
csv-parser3.534 - 3.612
csv-test-xs-200.409 - 0.434
test6.689 - 6.835
test-t1.430 - 1.527
test-t --race0.879 - 0.956
test-t-2021.286 - 22.157
test-t-20 --race7.095 - 7.390
 07:56
lizmat Files=1353, Tests=117192, 290 wallclock secs (35.28 usr 10.12 sys + 4035.75 cusr 336.58 csys = 4417.73 CPU) 09:00
Geth rakudo/lizmat-unitemize-meta: 9ed4fae856 | (Elizabeth Mattijsen)++ | 2 files
Restore .meta behaviour

on CompUnit::Repository::Distribution and Distribution::Path.
These were recently changed to return an unitemized hash, but apparently there's code out there that depended on the itemization behaviour.		 09:23
rakudo: lizmat++ created pull request #4896:
Restore .meta behaviour
IO-Path-ChildSecure/main: 577168a00c | (Elizabeth Mattijsen)++ | 9 files
First commit of updated module
 09:46
IO-Path-ChildSecure/main: 48e6c21c9b | (Elizabeth Mattijsen)++ | 2 files
1.1
 09:50
lizmat [Coke] ^^ :-) 09:51
Geth rakudo/lizmat-constantize-compiler-info: 7df9c34341 | (Elizabeth Mattijsen)++ | tools/cleanup-precomps.raku
Say how many bytes in files were freed

Typically 27 MB for just one setting re-compilation for yours truly		 10:59
DBIish/main: 88264f6d70 | (Rod Taylor)++ | .github/workflows/test.yml
Improve dependency installation success?

Dependency installation regularly fails during the cron'd time but succeeds if rerun. I presume starting on-the-hour results in busy servers, so try starting at a less standard minute (a largish prime) instead.		 11:40
rakudo/lizmat-fix-repo-chain-check: ea647c2d41 | (Elizabeth Mattijsen)++ | src/core.c/CompUnit/PrecompilationRepository.pm6
Fix repo-chain changes check

It was incorrectly checking the compilation unit ID against the what is considered the original first REPO.id in the chain. It should be checking against the *current* first REPO.id!		 12:04
rakudo: lizmat++ created pull request #4897:
Fix repo-chain changes check
Geth rakudo/lizmat-fix-repo-chain-check: d64686fc5a | (Elizabeth Mattijsen)++ | src/core.c/CompUnit/PrecompilationRepository.pm6
Make sure the RAKUDO_MODULE_DEBUG output matches
 12:14
rakudo/lizmat-fix-repo-chain-check: 02556e87a0 | (Elizabeth Mattijsen)++ | src/core.c/CompUnit/PrecompilationRepository.pm6
Actually refer to an existing variable :-(
 12:20
[Coke] lizmat: that commit changed the whole repo, it seems 12:28
lizmat ?? 12:29
ah, you mean ChildSecure
yes... basically it is now a distrubution handled by App::Mi6 12:30
*distribution
[Coke] but it also changed it from nqp to raku at the same time, yes? 13:20
lizmat yup
jdv just started hopefully the last blin run 14:16
japhb lizmat: 7df9c34341 defines gross-bytes but doesn't use it ... is that in preparation for a followup? 15:00
[Coke] jdv: any errors in the nqp test suite? 15:40
jdv i don't run that before the release usually 16:51
just blin
looks like there's still something up with Text::CodeProcessing and now Cro::ZeroMQ is unhappy too - latest blin 16:57
lizmat: do you think we should just ticket the T::CP one and leave it at that? 16:58
lizmat: also, could part of that C::ZMQ one be from the module work you've been busy at? 16:59
i'm gettin the feelin we might need to defer the release... 17:08
Geth rakudo/lizmat-constantize-compiler-info: a827fcae5e | (Elizabeth Mattijsen)++ | tools/cleanup-precomps.raku
Remove dead code, japhb++ for noticing

Originally I planned to report the actual size of the blocks freed but at least on (my) MacOS the reported block size and the number of blocks freed, was at least a factor 8 too large (which could very well be it reporting a block size of 4096, but actually working with 512 byte blocks). So I returned to just report the sum of the file sizes of the files removed. And forgot to remove the code that tried to calculate the raw size freed.
lizmat checks for a new blin run 17:09
jdv: will look at Text::CodeProcessing again, glad that Jupyter::Kernel is clean now (although it *was* naughty( 17:10
))
jdv thanks 17:11
what do you think about the other one?
i'm a bit more concerned at that
s/at/about/
lizmat I will look at that after I had a look at T:CP but it looks like it's a repo based issue, and I've been doing a lot in that area recently (although not on CURFS or CURI 17:13
I plan on working on this the coming 2.5 hours... if not fixed by then, I'll let you know 17:17
lizmat m: $answer ** 2 17:43
camelia ===SORRY!=== Error while compiling <tmp>
Variable '$answer' is not declared. Perhaps you forgot a 'sub' if this
was intended to be part of a signature?
at <tmp>:1
------> <BOL>⏏$answer ** 2
lizmat jdv ^^^ that error message has changed, and T::CP is checking for the *exact* error message.
I will make an issue
bisectable6: old=2021.12 $answer ** 2 17:46
bisectable6 lizmat, Bisecting by output (old=2021.12 new=522c5fc) because on both starting points the exit code is 1
lizmat, bisect log: gist.github.com/b5bdbec72e11a21dc2...65036f0e86 17:47
lizmat, (2022-03-23) github.com/rakudo/rakudo/commit/a5...ce933274f0
jdv lizmat: oh... thanks
lizmat github.com/antononcube/Raku-Text-C...g/issues/2 17:48
I'm leaving to the author how they want to fix that in a version independent way :-)
jdv nice 17:49
lizmat first, going to watch a SpaceX launch :-) 17:50
T-01:40
lizmat github.com/croservices/cro-zeromq/pull/4 18:46
jdv ^^ 18:47
the problem was caused by a defective META6.json file that was previously not seen because the tests used -Ilib rather than -I.
jdv lizmat: thanks 18:56
draft changelogs are up 18:57
lizmat looks
lizmat edits 18:58
jdv note i left my working list for your chunk at the bottom in case that helps 18:59
lizmat jdv: did we always include PR numbers in commit messages ?
jdv aside from spelling i normally take the pr and/or commit msg verbatim
i'm guessing that's from gh squashings?... 19:00
lizmat yeah... I don't think they make much sense in a changelog, if you also specify the commit(s)
jdv i don't think so though
[Coke] jdv: do you run 'make test' in rakudo before the release? 19:05
jdv of course 19:07
lizmat: are you editting now? cause i forgot to run releaseable to finish up and i need to add a few more. 19:09
[Coke]: just not a lot of free time, you know;)
lizmat jdv: just stopped editing for now 19:22
jdv: going to be afk for a bit... will be back in ~ 2 hours 19:25
jdv lizmat: cool, thanks 19:27
lizmat: i'm done 19:33
patrickb jdv: Did you notice github.com/rakudo/rakudo.org/pull/78 ? 20:21
Geth WebService-GitHub/main: 6 commits pushed by (Patrick Böker)++ 20:25
jdv patrickb: i did, but like [Coke], i'm not sure i have much to add. 22:01
i don't know zoffix's key either 22:02
what is non-typical about it? my key is on a keyserver somewhere. not sure what is meant by listing a key on a gh profile page. i know mine is at gh and i believe people can query it somehow if they wish - not sure why they would... 22:07
Geth rakudo: c029308938 | (Elizabeth Mattijsen)++ (committed using GitHub Web editor) | 2 files
Restore .meta behaviour

on CompUnit::Repository::Distribution and Distribution::Path.
These were recently changed to return an unitemized hash, but apparently there's code out there that depended on the itemization behaviour.		 22:26
rakudo: 4a7da9a161 | (Elizabeth Mattijsen)++ (committed using GitHub Web editor) | src/core.c/CompUnit/PrecompilationRepository.pm6
Fix repo-chain changes check

It was incorrectly checking the compilation unit ID against the what is considered the original first REPO.id in the chain. It should be checking against the *current* first REPO.id!
releasable6 Next release in ≈19 hours. There are no known blockers. Please log your changes in the ChangeLog: github.com/rakudo/rakudo/wiki/ChangeLog-Draft 23:00

Powered by Cro and the Raku® Programming Language.

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

Thank you!