Geth ¦ rakudo: vrurg self-assigned Rebuilding fails on older git github.com/rakudo/rakudo/issues/3266 00:46
rba I've singed up for github package registry for the perl6 github org. Mainly to try it out if the docker registry is usful. 05:31
Geth nqp/truffle: cb46cc8067 | (Paweł Murias)++ | 2 files
[truffle] Implement nqp::until
 09:21
AlexDaniel vrurg: oh, so it was resetting to v6.d in EVALs, and that's it? 09:42
just because that's the default?
that's kinda easy… I was staring at the behavior yesterday and just couldn't understand what's going on :D 09:44
AlexDaniel in my defense I was sleepy 09:44
anyway, thanks for fixing it!
Geth nqp/truffle: e413ae5425 | (Paweł Murias)++ | src/vm/jvm/runtime/org/perl6/nqp/truffle/nodes/control/NQPWhileNode.java
[truffle] Remove placeholder loop control

We need to reintroduce it properly thinking how we will deal with labels.		 10:05
nqp/truffle: 50ba8bc7b5 | (Paweł Murias)++ | src/vm/jvm/runtime/org/perl6/nqp/truffle/nodes/control/NQPWhileNode.java
[truffle] Stop inheriting from a wrong superclass

We need only a few lines from it and this class isn't called the way the superclass assumes. k#
nqp/truffle: 4f74b67d58 | (Paweł Murias)++ | src/vm/jvm/runtime/org/perl6/nqp/truffle/nodes/control/NQPWhileNode.java
[truffle] Implement repeat_while and repeat_until ops

The form with -> is NYI
sena_kun anyone wanting to get easy github points by merging some PRs? :) 12:13
AlexDaniel sena_kun: like wha? 12:17
:)
sena_kun github.com/perl6/roast/pull/587
github.com/perl6/roast/pull/590
;)
AlexDaniel Kaiepi: just let me know what we can do about it 12:21
AlexDaniel Kaiepi: we can revert or we can try to fix 12:21
tellable6 AlexDaniel, I'll pass your message to Kaiepi
Geth roast: 9f07cb4b57 | Altai-man++ | S32-list/seq.t
Test caching by elems call on Seq

Closes github.com/rakudo/rakudo/issues/2976		 12:23
roast: c0d9e58ef9 | (Aleks-Daniel Jakimenko-Aleksejev)++ (committed using GitHub Web editor) | S32-list/seq.t
Merge pull request #590 from perl6/elems-on-seq-cache

Test caching by elems call on Seq
AlexDaniel sena_kun: you *can* use is-deeply 12:27
m: use Test; my @t2482 = |<1 2> >>xx>> 2; is-deeply @t2482, [<1 1>.Seq, <2 2>.Seq]
camelia ok 1 -
AlexDaniel you just need to be precise 12:27
sena_kun: also, “Hyper on a slip values are correct”. Hmm “Hyper on slip values is correct”?
sena_kun hmm, I wonder why it didn't work. :/ thanks, will change it... yeah, the article is redundant for sure
AlexDaniel speaking of points 12:28
no squashathon winner was announced
but not because there was no winner, of course 12:29
more like because I'm a loser who struggles with multitasking :)
soo…
squashable6: status 2019-10-19
squashable6 AlexDaniel, Log and stats: gist.github.com/f86198c3246873cc24...c9d6fd915a
sena_kun AlexDaniel, you are doing some spectacular things here. 12:30
AlexDaniel ah come on, I should've checked 6.c/6.d -errata tests much earlier
AlexDaniel in fact, we should really add some automation for that 12:31
kawaii: ping? 12:32
kawaii: blin blin blin!
lizmat: are plushies still being sent out to squashathon winners? Is it still a thing? Either way, can we continue doing it? :) 12:38
kawaii pong! 12:41
Blin time yes sir
Kaiepi could blin wait until after i revert socket ops using all addresses hostnames resolve to? 13:08
tellable6 2019-10-24T12:21:43Z #raku-dev <AlexDaniel> Kaiepi: we can revert or we can try to fix
AlexDaniel Kaiepi: ideally we'd run it again afterwards too
Kaiepi ok
idt reverting all the changes in the pullreq that's from is a good idea because the way it changes how flags are handled when resolving makes hostname resolution a bit more efficient and fixes an error that would happen when resolving any kind of address on dragonflybsd 13:10
it's something i'd have to revert manually because of how messy the commits in it ended up though 13:14
vrurg AlexDaniel: I think test merges are better be postponed on after the release too. Don't you? 13:57
sena_kun vrurg, what tests do you refer to? 14:00
vrurg sena_kun: any PR in roast.
sena_kun: I was about to merge 587, but think it's better wait for release branching. 14:01
sena_kun vrurg, what's the reasoning? They don't affect anything in the implementation that is shipped, in fact they help to identify if anything previously fixed is busted on master. 14:02
vrurg I'm not in the details of the release process, worried if this could break anything. Though you're right. 14:03
sena_kun I can understand the "probably easier to release" argument, but I just don't see how roast affects the actual artifacts produced.
Geth roast/master: 4 commits pushed by Altai-man++, (Vadim Belman)++
sena_kun phew, I thought I was wrong for pushing people to merge. :)
AlexDaniel++ vrurg++ 14:04
AlexDaniel no, roast master doesn't affect that much 14:54
we're not shipping roast with rakudo releases, so no problem merging roast PRs
japhb AlexDaniel: #perl6-dev seems to have gone full silent. Time to change the topic, send join messages, etc. to catch future stragglers? 16:02
AlexDaniel japhb: travis is still reporting there… 16:03
japhb AlexDaniel: Really? I hadn't seen any such reports in several days, so I assumed it was no longer doing so.
AlexDaniel colabti.org/irclogger/irclogger_lo...2019-10-22 16:04
japhb OK, so ~ 2 days, 13 hours since last such. 16:05
AlexDaniel jnthn: I think it's some debug info that you left out: github.com/perl6/roast/blob/21d9b9...sics.t#L35 16:20
AlexDaniel idea: make Comma highlight lines with &dd in some noticable but not too irritating color :) 16:21
jnthn AlexDaniel: Hmm, "left in" perhaps? :)
AlexDaniel yeah
but, it's probably not even your test… I'm not sure
jnthn But yes, that looks unintended, and given what the test is covering, I might well be guilty :P 16:22
AlexDaniel it was added by Zoffix in this commit: github.com/perl6/roast/commit/6a59...1c56669c13 16:23
ok I'll just delete it
ok, now this: github.com/perl6/roast/commit/c068...611f072R53 16:24
it can be just `CATCH { default { } }`, right? 16:26
jnthn Maybe I'd make that one `diag` 16:31
Geth roast: 605573fa77 | (Aleks-Daniel Jakimenko-Aleksejev)++ | S07-hyperrace/basics.t
Remove accidentally committed debug code
 16:32
AlexDaniel that one we don't have in 6.c or 6.d :) 16:33
wait oops it should be in 6.d… 16:34
Geth roast/6.d-errata: adb9ab6703 | (Aleks-Daniel Jakimenko-Aleksejev)++ | S07-hyperrace/basics.t
Remove accidentally committed debug code
 16:35
AlexDaniel ok that CATCH thing doesn't even fire… 16:37
Geth roast: ac0fcd685d | (Aleks-Daniel Jakimenko-Aleksejev)++ | S32-io/socket-accept-and-working-threads.t
Remove unnecessary use of dd

  `dd` is a rakudo feature, and in this particular case it doesn't really
matter what is being used, so something that is compiler-agnostic is better.		 16:40
roast/6.d-errata: 3452f2f3ae | (Aleks-Daniel Jakimenko-Aleksejev)++ | S32-io/socket-accept-and-working-threads.t
Remove unnecessary use of dd

  `dd` is a rakudo feature, and in this particular case it doesn't really
matter what is being used, so something that is compiler-agnostic is better.
AlexDaniel OK, no dd in roast :)
unless I overlooked something 16:41
[Coke] www.nntp.perl.org/group/perl.perl5...56484.html p5 made the leap to github, including their RTs. 17:01
(I know we were next in line for the RT transition) 17:02
AlexDaniel [Coke]: not exactly, they actually expected us to go first :) 17:28
sort of 17:29
Kaiepi almost done making moarvm just use the first address a hostname resolves to again, just waiting for make spectest to finish up 17:37
tbrowder advice, please: i'm starting to try to implement pod $=data and need an object to have both Associative and Positional roles. i made a cursory attempt in basic nqp but had problems. i think i need to go toward 6model direction per nqp/docs/6model/overview. and start developing the class inside World.nqp. does that sound like the right direction? i'm pretty confident i can just do positional only for a start with an 19:22
array and put off the hash/array class until later.
i think i'll go the array only route for now, but advice on how to create the needed multi-role class would be helpful. 19:27
[Coke] Kaiepi++ 19:38
lizmat AlexDaniel: if winners give me the contact info, yes, then they will be sent :-) 20:18
sena_kun has two already and wonders if another one can be dedicated to someone 20:55
[Coke] thought only one was going out to any one person. 21:26
[Coke] has one in his home office which he loves dearly.
sena_kun to be fair, only one of mine is from squashathon. :] 21:35
discord6 <noelsken> as a process question, should I PR replacement of my deadname with my actual name from rakudo's CREDITS or is there anything in place yet for people with name changes? 21:45
<noelsken> I know that changing my git details is probably not possible without a lot of weird breakage at least :) 21:46
<noelsken> (hence the different github account in the first place)
AlexDaniel sena_kun: I won't be announcing any other winner this month, others didn't do more than one PR 21:48
tellable6 AlexDaniel, I'll pass your message to sena_kun
AlexDaniel sena_kun: so you decide what to do with it :)
tellable6 AlexDaniel, I'll pass your message to sena_kun
AlexDaniel noelsken: sure, please do submit a change to CREDITS! 21:49
I mean, feel free to :) 21:50
discord6 <noelsken> fwiw it's not legal yet so theoretically whatever that slip I signed to get commit access to github/rakudo is still legally valid, but I don't know in how far that's transferable to a different github account 21:51
<noelsken> plus I've been gone a while and lost at least some insight into processes and who to talk to wrt a thing or another... :) 21:52
Geth rakudo/name-change-peschwa: 9632dc21c3 | peschwa++ (committed using GitHub Web editor) | CREDITS
Update CREDITS

due to personal reasons I'd like this changed		 21:53
discord6 <noelsken> ah github web 21:54
<noelsken> I did not mean to create that branch on rakudo/rakudo whoops
Geth rakudo: peschwa++ created pull request #3267:
Update CREDITS
rakudo: 9632dc21c3 | peschwa++ (committed using GitHub Web editor) | CREDITS
Update CREDITS

due to personal reasons I'd like this changed		 21:55
rakudo: cfc0f46c0b | (Aleks-Daniel Jakimenko-Aleksejev)++ (committed using GitHub Web editor) | CREDITS
Merge pull request #3267 from rakudo/name-change-peschwa

Update CREDITS
AlexDaniel noelsken: by the way, you can also keep U: psch U: peschwa entries
if you want others to find you based on your old handle
discord6 <noelsken> yeah that's a bit double-edged 21:56
<noelsken> I don't really want to be found by my old handle, but I understand how it's useful
AlexDaniel if you don't want then don't do it, it's totally fine
discord6 <noelsken> I'm gonna stick with it as-is for now I think :)
<noelsken> yup, thanks :) 21:57
AlexDaniel as for git history, that we can't change I'm afraid
discord6 <noelsken> yeah, I accept that
<noelsken> even if rakudo/rakudo would change it that wouldn't do anything but break a lot of things downstream everywhere, and that's just not necessary 21:58
<noelsken> well, rakudo/rakudo and all the perl/ repos I contributed to and ... shrug
AlexDaniel we can create a .mailmap file though 22:00
but that will explicitly tell about the change 22:01
noelsken: on github you can change your name and even username, and the commits will link to your account 22:02
it works based on the email address that you have attached to your account 22:03
and you can have more than one email 22:04
discord6 <noelsken> I might not have researched enough before making a new github account instead of changing the display info on my old one... :)
AlexDaniel you can still do it
“After changing your username, your old username becomes available for anyone else to claim.” 22:05
so you can rename your new account and the rename the old account
then*
see help.github.com/en/github/setting-...b-username
discord6 <noelsken> huh, I'll have to read into that 22:06
<noelsken> it's a bit late here :)

Powered by Cro and the Raku® Programming Language.

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

Thank you!