lizmat Files=1295, Tests=109679, 209 wallclock secs (28.06 usr 8.26 sys + 2927.91 cusr 275.24 csys = 3239.47 CPU) 08:22
[Tux] Rakudo version 2019.11-438-g0e9f96ea9 - MoarVM version 2020.01-15-g1fa9764bf
csv-ip5xs0.735 - 0.866
csv-ip5xs-206.615 - 7.420
csv-parser24.854 - 25.884
csv-test-xs-200.433 - 0.475
test7.671 - 7.771
test-t1.852 - 1.860
test-t --race0.848 - 0.868
test-t-2030.897 - 32.117
test-t-20 --race9.308 - 9.671
 09:56
Geth rakudo/release-2020.01: 3fa7ed0068 | Altai-man++ | docs/announce/2020.01.md
More updates to changelog

Deliberately not logged:
29260ac 27d1c4b aa9c824		 11:17
rakudo/release-2020.01: e2fcb181f5 | (Stefan Seifert)++ (committed by Altai-man) | src/core.c/CompUnit/PrecompilationRepository.pm6
Fix missing dependency information when precompiling large dependency trees

The precompilation process writes dependency information to STDOUT from which it is read by the parent process. STDOUT is buffered by default when it's not connected to a tty. Apparently we do not always flush the buffer on program exit, so instead, flush every line immediately when written. There are usually not that may anyway. Fixes "Missing or wrong version of dependency" issue in a large proprietary code base.
Altai-man_ cherry-picked the fix commit. as soon as there will be a fix for github.com/rakudo/rakudo/commit/63...417996793a and Module::Toolkit failure, November failure and ADT failure, we're ready for a release. 11:19
lizmat Altai-man_: what did that commit break ? 11:27
Altai-man_ lizmat, constant::overload module
lizmat overload::constant ? 11:28
Altai-man_ oops, yes 11:29
lizmat looking at it now
Geth ¦ problem-solving: lizmat assigned to jnthn Issue Add Str.(r)index(@needles) github.com/Raku/problem-solving/issues/148 12:09
lizmat Altai-man_: I have *no* idea what is causing the error: all calls to `return` in that section of code, have been wrapped into a `try` already :-( 12:22
tellable6 lizmat, I'll pass your message to Altai-man_
sena_kun :S 12:40
tellable6 2020-01-12T20:05:40Z #raku-dev <nine> sena_kun: github.com/rakudo/rakudo/commit/9f...25ae987f72 is definitely recommended for the release. It fixes a critical issue with ~0 chance for a regression.
sena_kun this is sad
AlexDaniel it's alright :) 12:57
eventually we'll get the release out 12:58
jmerelo It's that time of the year again when we are looking for project ideas for Google Summer of Code, for which we intend to apply perl-foundation-outreach.github.io...020-ideas/ 13:35
Please submit your ideas as a new document via PR, or discuss them in the issue for it.
lizmat notable6: weekly 13:45
notable6 lizmat, 2 notes: 2020-01-08T17:57:05Z <lizmat>: andrewshitov.com/2020/01/08/callin...interface/ ; 2020-01-09T08:36:44Z <lizmat>: github.com/drforr/raku-OLE-Storage_Lite
lizmat notable6: weekly reset
notable6 lizmat, Moved existing notes to “weekly_2020-01-13T13:45:37Z”
lizmat jmerelo: the GSOC request is already in the next weekly :)
jmerelo lizmat: thanks! 13:47
nine As commit 63f117502a93b4 is a performance improvement, we could just revert it on the release branch and figure out how it breaks that module on our own time without release pressure 17:13
lizmat nine: you cannot just revert that commit, we'd need to re-instate sub THROW as well 18:00
tellable6 hey lizmat, you have a message: gist.github.com/77e66665db40e3b520...940187e2e5 18:01
lizmat and another Rakudo Weekly News hits the Net: rakudoweekly.blog/2020/01/13/2020-...nt-things/ 21:42
pyrimidine lizmat++ 22:34
Geth rakudo: patrickbkr++ created pull request #3422:
Implement `--git-reference` Configure.pl option		 23:54
nqp: patrickbkr++ created pull request #595:
Implement `--git-reference` Configure.pl option		 23:55
nqp-configure: patrickbkr++ created pull request #15:
Implement `--git-reference`, remove `--reference`

Powered by Cro and the Raku® Programming Language.

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

Thank you!