vrurg AlexDaniel: github.com/perl6/problem-solving/projects/1 00:43
AlexDaniel [Coke]: it should be working… 00:44
vrurg: nice
vrurg AlexDaniel: I'm trying to stick 6.e labels to where they applicable, but could miss some issues. So, if you think something worth planning for 6.e... 00:46
AlexDaniel vrurg: I don't know of any blockers for 6.e 00:48
it doesn't mean we have to do everything 00:49
vrurg Sure we don't. The point of the project is to track whatever we consider ok to be part of 6.e
vrurg could probably find things planned for 6.d which are gonna be postponed to 6.f... ;) 00:50
Geth ¦ problem-solving: vrurg assigned to jnthn Issue Add Dict/Tuple to the core github.com/perl6/problem-solving/issues/135 00:58
travis-ci Rakudo build failed. Aleks-Daniel Jakimenko-Aleksejev 'Keep previous format for next releases' 01:04
travis-ci.org/rakudo/rakudo/builds/617441765 github.com/rakudo/rakudo/compare/b...3ed87fdfca
travis-ci Rakudo build passed. Aleks-Daniel Jakimenko-Aleksejev 'Keep previous format for next releases' 01:24
travis-ci.org/rakudo/rakudo/builds/617441765 github.com/rakudo/rakudo/compare/b...3ed87fdfca
vrurg just realized Configure.pl is broken with regard to updating NQP repository when a bump took place. 01:48
Sorry, but will only be able to fix it tomorrow. :(
A quick work around for this is wiping out nqp subdir. 01:50
lizmat Files=1290, Tests=109645, 208 wallclock secs (28.28 usr 8.16 sys + 2917.98 cusr 266.27 csys = 3220.69 CPU) 12:10
[Coke] would like to set a bounty for resolution of github.com/rakudo/rakudo/issues/3057 15:31
[Coke] m: Date.new(now) - Date.new(<2019-06-13>) 15:32
camelia WARNINGS for <tmp>:
Useless use of "-" in expression ".new(now) - Date.new(<2019-06-13>)" in sink context (line 1)
[Coke] m: say Date.new(now) - Date.new(<2019-06-13>) 15:32
camelia 167
japhb [Coke]: OOC, why Date.new(now) instead of Date.today? Delta carrying the formatter around they're equivalent, but the latter seems clearer in that it hides the conversion from Instant. 16:01
[Coke] was shorter to type. :) 16:04
I agree, .today is clearer
[Coke] m: say .today - .new(<2019-06-13>) given Date 16:05
camelia 167
lizmat github.com/perl6/problem-solving/i...-559191230 17:53
japhb lizmat++ # Thank you. 18:03
Geth roast: 5a68237b50 | (Elizabeth Mattijsen)++ | S32-temporal/Date.t
Add test for R#3069
 18:55
japhb Woo-hoo! rebuild-all for November release and my usual module list worked! 19:18
But wait, why isn't the new MoarVM release showing up in the version info? "This is Rakudo version 2019.11-51-g093ed87fd built on MoarVM version 2019.07.1-322-g8d0b50d3f" 19:19
Missing tag in MoarVM?
Geth roast: 4e957508b0 | (Tom Browder)++ (committed using GitHub Web editor) | S26-documentation/block-leading-user-format.t
Add test for user-formatted pod leading declarator blocks (#591)
 19:57
vrurg_ japhb: you'd have to pull it with --tags, perhaps. 19:58
.tell Kaiepi I guess this could be related to your work: github.com/rakudo/rakudo/issues/3326
tellable6 vrurg_, I'll pass your message to Kaiepi 19:59
Geth roast/revert-591-master: 407f0c79d2 | (Tom Browder)++ (committed using GitHub Web editor) | S26-documentation/block-leading-user-format.t
Revert "Add test for user-formatted pod leading declarator blocks (#591)"

This reverts commit 4e957508b059acd4ae551f5105a213bb58776b31.
Kaiepi i'll take a look vrurg 20:03
vrurg Kaiepi: thanks! 20:04
japhb vrurg: Yup, git pull --tags fixed. After reading through the git pull and git fetch docs, I have to say: WHY DO WE EVEN HAVE THAT LEVER? 20:19
[Coke] remembers writing docs for work that explained that --all didn't include --tags. 20:20
japhb Also, I wonder what got lost in the release that this wasn't automatic ... no merge of the release branch back to master maybe? That's what glg seems to be indicating.
[Coke]: "But why?" -- this is one of those "goofy default" cases. 20:21
vrurg japhb: did you do pull manually? 20:24
japhb vrurg: I have a script that pulls and rebuilds everything from scratch. (It doesn't pull into working directories; it pulls into bare repos, and then local-clones them into build dirs, checks out HEAD or a requested rev, and builds from there.) 20:58
Basically I have seen the entire history of utterly broken builds, and so the script has been slowly bullet-proofed over years for every time someone messes with the repos. :-/ 20:59
japhb I've lost count of the number of times the official recommendation was "Welp, blow away your checkout and try again" -- which was after the "Always git clean -dXf" era 21:01
vrurg japhb: I was wondering to know if the pull which Configure.pl does needs --tags too. 21:02
vrurg is afk
japhb vrurg: Seems wise. :-)
TBH if not for the network cost of pulling down repos at this point, I might just clone my build trees completely from scratch from GH. On the (now-rare) occasions I hack on rakudo itself, I have a separate clone for that. 21:04
.oO( Disk is cheap ... THANKFULLY )
AlexDaniel japhb: not really, it's still kinda pricey to get tens of TBs 21:45
:)
japhb Perspective on disk space is a little different at japhb.dayjob ... 22:00
But even at home, Costco's cheapo backup drives are now bigger than I actually need.
I suppose if I was trying to build a server farm out of pocket, it would add up. :-) 22:01
Geth rakudo: 872cb7c002 | (Elizabeth Mattijsen)++ | src/core.c/hash_slice.pm6
Make the decont operator about 20x faster

Thanks to Peter du Marchie van Voorthuysen for spotting this.
Fixes R#3327		 22:20
Geth rakudo: 1945b9d27c | (Vadim Belman)++ | tools/lib/NQP/Config/Rakudo.pm
Fix incorrect behavior of nqp checkout

Must only be skipped if `--force-rebuild` is used.		 23:02
Kaiepi i need to double check that my benchmarks are accurate, but #3326 may be pretty simple to fix 23:25
R#3326
bah, github.com/rakudo/rakudo/issues/3326

Powered by Cro and the Raku® Programming Language.

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

Thank you!