Geth roast/master: 4 commits pushed by (Daniel Lathrop)++, (Juan Julián Merelo Guervós)++ 07:15
roast: e71de9edba | (Daniel Lathrop)++ (committed using GitHub Web editor) | rosettacode/greatest_element_of_a_list.t
Update rosettacode link to use #Raku
 07:16
roast: 666ae25d18 | (Daniel Lathrop)++ (committed using GitHub Web editor) | rosettacode/sierpinski_triangle.t
Update rosettacode comment to use #Raku url
roast: b59b74a22e | (Juan Julián Merelo Guervós)++ (committed using GitHub Web editor) | 2 files
Merge pull request #664 from lathropd/lathropd-patch-1

Rosettacode comment updates
JJMerelo Did you know you can say "no strict" in Raku? Well, you can but nobody has used it, apparently. moritz tells us all in today's 20th anniversary post raku-advent.blog/2020/08/10/rfc-64...t-scoping/ 07:51
tellable6 2020-08-09T12:15:10Z #raku <ab5tract> JJMerelo can you ping me in private when you get online? In the end I could use a new advent invite to a different email address
2020-08-09T20:22:57Z #raku <ab5tract> JJMerelo if you could send the invite to my email in CONTRIBUTORS that would be awesome. if not, no worries -- the post will be live and pre-published for Tuesday mid-morning tomorrow no matter what
JJMerelo .tell ab5tract will do. Also, online now.
tellable6 JJMerelo, I'll pass your message to ab5tract
JJMerelo .tell leont we need your article just about now... Down to one article scheduled 07:54
tellable6 JJMerelo, I'll pass your message to leont
leont Sorry about that delay 07:55
Will make sure it is finished today 07:56
JJMerelo Thanks, leont 08:15
lizmat m: no strict; $a = 42; say $a 08:53
camelia 42
lizmat m: my int @a; dd @a.min # this feels like an argument for having ().min return Nil 08:56
camelia Inf
lizmat JJMerelo: do you need more articles still? 08:57
*we
JJMerelo Yep, we do.
lizmat ok, I'll go through the RFC's again
JJMerelo Even if all those that have been committed are submitted on time, we're like 6 short of the full calendar
I check every morning and have a couple of RFCs lined up, to write something fast if reserve becomes 0, but any collaboration is appreciated. 08:58
jnthn What's the deadline? I was thinking to write one. 09:14
sena_kun jnthn, the sooner the better, 20th is the day for last article, I think.
jnthn, by the way, I guess you saw, but #cro 09:16
lizmat hopes ugexe or nine might want to do one about raku.org/archive/rfc/78.html 09:18
Kaiepi what do i need to do to deprecate a method? 10:18
i know there's a process for it, but i can't find examples of what i'm thinking of on master
Geth nqp: d2a35ac5ac | (Patrick Böker)++ | 6 files
Add a HLL::SysConfig class

This class acts as a central point where configuration information is stored. The class should only ever be accessed via
  `nqp::gethllsym('default', 'SysConfig')`. This then allows the class to be
overridden by a subclass.		 10:19
nqp: 1c26c65c59 | (Patrick Böker)++ (committed using GitHub Web editor) | 6 files
Merge pull request #653 from patrickbkr/sysconfig

Add a HLL::SysConfig class
tobs If anyone else is looking for RFCs to write about, I think #190 is doable. I've been meaning to write a second one, but time is scarce, so feel free to take that. 10:28
nine Build broken: [ 88s] Unhandled exception: Cannot find method 'config' on object of type Perl6::Compiler 10:31
[ 88s] at gen/moar/rakudo.nqp:1 (rakudo.moarvm:<mainline>)
Geth rakudo/master: 4 commits pushed by (Patrick Böker)++ 11:10
lizmat notable6: weekly 11:44
notable6 lizmat, 2 notes: 2020-08-04T18:39:22Z <guifa2>: github.com/alabamenhu/DateTimeTimezones ; 2020-08-08T17:42:31Z <guifa2>: github.com/demostanis/hubtodate/re...s/tag/v0.4
lizmat shouldn't hubtodate be in the ecosystem? Or am I missinge something? 11:46
*missing
notable6: weekly reset 11:47
notable6 lizmat, Moved existing notes to “weekly_2020-08-10T11:47:03Z”
patrickb o/ 11:53
tellable6 2020-08-07T14:17:47Z #raku-dev <vrurg> patrickb: Unfortunately, I'm not sure I will have time for this soon. We've got a disaster at work, lost whole data center.
patrickb nine: I think you observed breakage because you tried to build with the nqp PR merged, but not the rakudo PR. Those depend on each other and the breakage was expected. Can you retry with both PRs merged? 11:54
Geth rakudo: patrickbkr++ created pull request #3843:
Revert "Skip dying tests to unbreak master builds"		 11:57
rakudo: b5443c28c0 | (Patrick Böker)++ | t/09-moar/01-profilers.t
Revert "Skip dying tests to unbreak master builds"

This reverts commit 51ea87a3e76324b3c232e26cf5e3e7ea339c17f7. As a PR to fix the profiling was merged, we re-enable the tests now.		 12:03
rakudo: a6509a38e3 | (Elizabeth Mattijsen)++ (committed using GitHub Web editor) | t/09-moar/01-profilers.t
Merge pull request #3843 from patrickbkr/re-enable-profile-tests

Revert "Skip dying tests to unbreak master builds"
lizmat And another Rakudo Weekly News hits the Net: rakudoweekly.blog/2020/08/10/2020-...ey-please/ 12:31
patrickb Given we move to a PR only policy, do we want to allow bumping moar and nqp without a PR? (The post bump code is already tested in the MoarVM and NQP CIs respectively). 12:35
sena_kun patrickb, no. 12:36
Or, hmmmmmm.
Hard to say.
Disregard that 3 lines above. 12:37
patrickb sena_kun: Maybe some more thinking is needed. I'm currently working on a solution document for prob-solving#206. Questions like these are relevant. 12:39
Geth nqp: 36670be517 | (Patrick Böker)++ | tools/templates/MOAR_REVISION
Bump MoarVM

This pulls in a fix for regex matching empty strings with the :i modifier.		 12:40
sena_kun patrickb++ 12:41
Geth rakudo: a84952fb13 | (Patrick Böker)++ | tools/templates/NQP_REVISION
Bump NQP (and thus MoarVM)

This pulls in a fix for regex matching the empty string with the :i modifier.		 12:43
roast: d31d359908 | (Patrick Böker)++ | 2 files
Test for empty string match with ignore-case and ignore-mark

Related to rakudo/rakudo#3815.		 12:45
roast: 81fb8c7cbd | (Patrick Böker)++ (committed using GitHub Web editor) | 2 files
Merge pull request #655 from patrickbkr/i-m-empty-string-match

Test for empty string match with ignore-case and ignore-mark
linkable6 RAKUDO#3815 [closed]: github.com/rakudo/rakudo/issues/3815 Regex :i modifier prevents empty string regex to match
patrickb .tell tony-o Can you have a look at github.com/tony-o/perl6-pluggable/pull/15 ?
tellable6 patrickb, I'll pass your message to tony-o
[Coke] so are we doing PR only on master now? saw a comment in recent scrollback but no discussion. 16:37
Geth roast/master: 5 commits pushed by (Daniel Lathrop)++, (Juan Julián Merelo Guervós)++ 16:40
sena_kun [Coke], there was no official, erm, guildelines or something like this yet, but (I hope) it is likely to become a policy somewhere in the future, so yes, it is preferred. 16:50
releasable6, status
releasable6 sena_kun, Next release in ≈12 days and ≈2 hours. 2 blockers. Changelog for this release was not started yet
sena_kun, Details: gist.github.com/917d75e40a52eb5642...5229972d35
[Coke] sena_kun: +1 16:58
lizmat [Coke] there was only grumbling when *I* did something to break master, yet there was none when other people broke the release 17:47
lizmat which was a signal for me to not do any work on core anymore 17:48
afk&
[Coke] I think doing PRs into master makes sense, but it's unfortunate that you were singled out. Sorry about that 17:53
Altai-man lizmat, I think my rant on certain problem-solving issue mentions master breakages by Patick, niner, MasterDuke at the very least. I also remember Jonathan being grumpy for next-dispatcher case implemented by vrurg originally. It is kind of heartbreaking to hear the amount of rant here was too much, because I truly admire your perseverance with this, but also perseverance of the above mentioned folks who do decent deeds because their spirit is 18:25
strong enough to do it.
IME, blaming contributors or being unthankful is next thing to telling them to go away. I still think that if development process can make delivering some quality cheaper for developers, we should go for it. 18:27
vrurg_ Correct me if I'm wrong, but the most disagreement was around committing directly into master and bypassing PRs with CI checks.
tellable6 hey vrurg_, you have a message: gist.github.com/b4b942639b3906ac5f...fb18c43168
vrurg Altai-man++ 18:28
lizmat: BTW, I also had a few unpleasant moments after merging my work on roles. The point is that you're one of the most committing persons around. So, your chances of breaking something are higher than anybody's else. :) 18:32
AlexDaniel` lizmat: I don't think the grumbling was ever directed at you, just at the changes you happened to make. Given the amount of work you do it is somewhat inevitable. 19:37
AlexDaniel` Generally, considering that you tend to work on optimizations and roast is not full enough to cover all of the edge cases, I can see how there can be a perception that you break things. But when I was the release manager you always responsibly worked on fixing the regressions, so I was very happy with your work 19:39
but I'd still prefer a PR-based workflow for other reasons
I'm right now like… 50% into refactoring the build process in whateverable… I hope… That should include the support for webhooks 19:40
this way bots will be able to run stuff here on the channel without a lot of delay (just the time it takes to build rakudo)
leont .tell JJMerelo I'm working on it. Almost done! 22:51
tellable6 leont, I'll pass your message to JJMerelo

Powered by Cro and the Raku® Programming Language.

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

Thank you!