Geth rakudo/nom: 6c76ed0abe | (Nick Logan)++ (committed using GitHub Web editor) | src/core/CompUnit/Repository/Installation.pm
Remove superfluous .IO
00:15
[Tux] This is Rakudo version 2017.07-5-g6c76ed0ab built on MoarVM version 2017.07 07:11
csv-ip5xs 2.767
test 13.061
test-t 4.243 - 4.321
csv-parser 12.177
samcv o/ 08:22
Geth perl6-lwp-simple: cpin++ created pull request #16:
Delete method sends headers
09:13
lizmat Files=1215, Tests=65558, 219 wallclock secs (13.29 usr 4.91 sys + 1321.98 cusr 138.56 csys = 1478.74 CPU) 09:20
Geth rakudo/nom: d82db18f3a | (Elizabeth Mattijsen)++ | src/core/set_addition.pm
Simplify infix:<(+)>(**@p) candidate

With all of the necessary candidates and testing for them in place, we can now do that
09:27
perl6-lwp-simple: 685dbbf1ff | cpin++ | 2 files
Delete method sends headers
10:04
perl6-lwp-simple: 37fffecb96 | cpin++ | t/delete-headers.t
Delete test says Delete (not Get)
perl6-lwp-simple: 048dfc6763 | (Zoffix Znet)++ (committed using GitHub Web editor) | 2 files
Merge pull request #16 from cpin/delete-headers

Delete method sends headers
perl6-lwp-simple: 27c77f8da5 | (Zoffix Znet)++ (committed using GitHub Web editor) | META6.json
Bump version
nine jnthn: so what do you think? Use subclasses for $*IN, $*OUT, $*ERR with an overwritten DESTROY or just have IO::Handle::DESTROY handle those file descriptors specially? 10:08
lizmat leans to the latter 10:10
jnthn I was hoping somebody else would do the thinking :P 10:11
But the most expedient is probably just to detect those handles in DESTROY :)
geekosaur usually those file descriptors get special cased in one way or another. old perl's $^F is an example
nine jnthn: ah, ok. With your investigation, this now seems like a rather trivial bug to fix
jnthn nine: Yes, I figured so, thus why I moved on to the spesh type planner, which I doubt anybody else will do if I don't. :-) 10:13
Zoffix What about .close? Should one be able to .close handles with 0, 1, 2 descriptors? 10:38
nine Zoffix: yes 10:39
Zoffix m: $*IN.close; $*IN.open; lines.say
camelia Reading from filehandle failed: Bad file descriptor
in block <unit> at <tmp> line 1
Zoffix How do you get 'em back, after you close them? 10:40
nine You don't :)
I think that's the point ;)
Zoffix OK
jnthn Indeed, once they're gone they're gone 10:46
Zoffix cues www.youtube.com/watch?v=0G3_kG5FFfQ 10:48
ZOFFLOP: t/spec/S11-modules/require.t 10:50
ZOFVM: Files=1252, Tests=161171, 132 wallclock secs (22.33 usr 3.40 sys + 2757.61 cusr 185.54 csys = 2968.88 CPU)
Geth rakudo/nom: 0e578c4fea | (Zoffix Znet)++ | src/core/IO/Handle.pm
Don't close standard handles in DESTROY

  'cause you can't get them back. If the user planned to actually close
them, they should do so via .close method.
Fixes RT#131755: rt.perl.org/Ticket/Display.html?id=131755
10:51
synopsebot6 Link: rt.perl.org/rt3/Public/Bug/Display...?id=131755
roast: f739f03ff4 | (Zoffix Znet)++ | S32-io/open.t
Unfudge standard handle reopen tests

Rakudo fix: github.com/rakudo/rakudo/commit/0e578c4fea RT#131755: rt.perl.org/Ticket/Display.html?id=131755
10:52
synopsebot6 Link: rt.perl.org/rt3/Public/Bug/Display...?id=131755
Geth roast: 9a85e42a6e | (Zoffix Znet)++ | S32-io/open.t
Test .DESTROY doesn't close standard handles

Rakudo fix: github.com/rakudo/rakudo/commit/0e578c4fea RT#131755: rt.perl.org/Ticket/Display.html?id=131755
10:56
synopsebot6 Link: rt.perl.org/rt3/Public/Bug/Display...?id=131755
rakudo/nom: d7fcb314e9 | (Elizabeth Mattijsen)++ | src/core/set_difference.pm
Streamline infix:<(+)>(**@p) candidate

  - with all of the necessary candidates and testing in place, we can now do that
  - makes $s (-) $s (-) $s on a 26 elem set about 1.5x faster
  - much less memory hungry, test shows 1/3 of garbage collections
11:19
lizmat grrr flaky wifi
argh.... copy pasto (-) !! 11:20
stmuk pl6anet.org/drop/rakudo-star-2017.07-RC0.tar.gz 11:42
Zoffix heh, SixFix has a very interesting learning curve. 12:31
Day 1: basic of basics 1-line problem. Day 2: basic of basics 1-line REPL problem. Day 3: Here's 174-line command line processing script. Let's get cracking! 12:32
also not very interesting since atom can jump to a line without any scripts :/ 12:33
mst SixFix? 12:40
Zoffix mst: sixfix.nigelhamilton.com/ 12:47
lizmat commute& 12:48
jnthn Zoffix: Can we close rt.perl.org/Ticket/Display.html?id=131755 now? 12:49
Zoffix Closed. 12:52
jnthn yay :) 12:53
2 more and we'll be back to 33 pages of tickets instead of 34 :P
[Coke] thought there was just one really big page. :)
jnthn Guess there's different ways of viewing it :) 12:54
[Coke] suspects we could close 100 todo/nyi tickets with "not going to happen"
Geth rakudo/nom: a0775e5e95 | (Elizabeth Mattijsen)++ | src/core/set_multiply.pm
Simplify infix:<(.)>(**@p) candidate

With all of the necessary candidates and testing for them in place, we can now do that
rakudo/nom: 2f5a6cd9a4 | (Jonathan Worthington)++ | src/vm/moar/ops/container.c
Ensure Scalar fetch can never return a NULL.
13:21
dogbert17 lizmat: do you know if tests have been added for RT #130366 ? 14:26
synopsebot6 Link: rt.perl.org/rt3/Public/Bug/Display...?id=130366
pmurias jnthn: do you think dropping support for some of the unused continuation features would be ok? 15:04
jnthn pmurias: Dropping support in what sense? 15:05
The tests are already per backend for whatever it supports; MoarVM's are less inclusive than the JVM ones
So if you don't wish to implement the case on the JS backend just don't include the tests for that case :) 15:06
pmurias jnthn: any plans to make rakudo use the case with 1? 15:12
jnthn pmurias: I'm not 100% confident saying "no" in that I'm still working on the non-blocking `await` 15:13
pmurias: I mean, it seems unlikely
pmurias why do we have per backends tests? 15:17
jnthn: waiting till you get the non-blocking `await` done before trimming the ops seems resonable 15:18
Zoffix m: say "\c[woman juggling: medium-dark skin tone]" 15:33
camelia ????????ā€ā™€ļø
Zoffix cool, `:` works now
AlexDaniel yup, samcv++ 15:37
.tell MasterDuke Malformed UTF-8 issue does not seem to be CATCH-able. I didn't really dive into this, but I guess if it happens in Proc::Async somewhere then you won't be able to handle it (as it is in a different thread)? 15:44
yoleaux AlexDaniel: I'll pass your message to MasterDuke.
ugexe wouldnt you use QUIT and not CATCH? 16:00
AlexDaniel ugexe: that's a good point 16:28
Geth rakudo/nom: 91be8bc1ca | (Zoffix Znet)++ (committed using GitHub Web editor) | src/core/Backtrace.pm
Remove "evil hack" comment ????????????

The comment is outdated in as much it was introduced when a full path was used. We examining the filename in several other places for this purpose in the class, so I'd dispute the claimed evility.
Closes RT#131757: rt.perl.org/Ticket/Display.html?id=131757
16:30
synopsebot6 Link: rt.perl.org/rt3/Public/Bug/Display...?id=131757
Zoffix I can't believe no one fixed the encoding problem in logs still :/ 16:32
Especially since #mojo too uses it.
AlexDaniel ugexe: butā€¦ that's not exactly how it works 16:35
ugexe: the problem is that somewhere in the code ā€œMalformed UTF-8ā€ issue pops out (possibly due to rakudo bug), and there's no way I can catch it from the outside
so the whole program goes down when it happens 16:36
now, what if I set the ā€œquitā€ thingy for both tapsā€¦ 16:37
that works \o/ 16:39
jnthn If you're using .tap without a quit, then the exception is unhandled
Note that this is a big reason to use react/whenever :)
AlexDaniel well, I know that I created too many trap issues, butā€¦ sounds like a trap to me 16:44
jnthn ??
What's it supposed to do with async error, drop it on the floor?
It behaves just like a sync exception if you don't write a CATCH
AlexDaniel well, I'm not saying that what it does is wrong
but if I just wrapped my whole program in a try CATCH, I'm kinda expecting that the whole thing won't go down
and then I'm using Proc::Async somewhere to shell out some little thingā€¦ and possibly even just Proc now
jnthn It's likely that error handling needs to be featured much more prominently in the docs
Also, most likely, a lot less examples that call .tap
And a lot more than use react/whenever
(The concurrency docs, to be clear) 16:45
Zoffix moritz: yo. How to debug the log encoding issue? If I clone the repo and try to run it, it tells me there's no backened.conf file. How can I play with the code and fix the problem? 16:48
Hm. There's ./install script.
AlexDaniel .tell MasterDuke nevermind. It's just that I'm an idiot: irclog.perlgeek.de/perl6-dev/2017-...i_14882744 16:49
yoleaux AlexDaniel: I'll pass your message to MasterDuke.
Zoffix man, there's no config/bot.conf.example :| 17:02
oh in the repo 17:03
this thing better have encoding issues when I finally launch it 17:04
ā™„ 17:05
And it's not there :( 17:07
.tell moritz so I launched my own ilbot on v5.24.0 and there ain't no encoding issues. Is it possible the database was exported/imported incorrectly when the box was upgraded? I'm sick of broken logs and I wanna fix the issue. How? 17:09
yoleaux Zoffix: I'll pass your message to moritz.
AlexDaniel does anybody have a working example using react/whenever and Proc::Async? 17:25
ugexe AlexDaniel: github.com/rakudo/rakudo/blob/nom/...ry.pm#L263 17:26
AlexDaniel ah, $proc.start is in whenever also. Interesting
ugexe that makes sure its not called until everything is tapped
AlexDaniel well, I thought that putting something like await $proc.start before whenevers will do it also 17:27
ugexe maybe await $proc.start *after* the whenevers, but certainly not before 17:28
AlexDaniel well, you can try it and see what happens ;) 17:29
oh, actually it kinda works 17:30
I just didn't have the patience to wait until the program finishes to see any lines of the output (when doing $proc.start *after*) 17:31
Geth roast: 9b51341b6c | (Elizabeth Mattijsen)++ | S03-operators/set_difference.t
Add one more edge case test + disable debug helper
17:38
samcv good * 21:46
Zoffix * 21:55
samcv has anybody ever had it happen when you make changes to a file but git diff doesn't show them
Zoffix Yup, when it's not tracked (e.g. a new file). git status would tell you if it is 21:57
Also: editing the file in the wrong place :)
samcv not in that case
hmm unless i pushed these cdhanges but. i can't see it... 21:58
ugh what
samcv checks rakudo/rakudo on github to ensure she's not crazy
ok i must have pushed some change. when did this happen. or someone else did 22:00
on my suggestion
samcv checks git blame 22:01
ok it was lizmat :)
ok i'm *not* crazy :P
AlexDaniel yay, -2 open tickets! :) rt.perl.org/Ticket/Display.html?id=126063 22:06
Zoffix buggable: tags 22:07
buggable Zoffix, Total: 1621; BUG: 1073; UNTAGGED: 371; LTA: 171; NYI: 95; JVM: 60; RFC: 57; REGEX: 56; CONC: 51; TESTNEEDED: 33; UNI: 27; PERF: 26; SEGV: 26; IO: 22; NATIVECALL: 22; REGRESSION: 22; POD: 21; @LARRY: 20; TODO: 18; PRECOMP: 14; BUILD: 11; OO: 11; TESTCOMMITTED: 11; OPTIMIZER: 10; STAR: 7; BOOTSTRAP: 5; REPL: 5; GLR: 4; MATH: 4; OSX: 4; WEIRD: 4; SPESH: 3; WINDOWS: 3; RT: 2; BELL
Zoffix ZofBot: only 1621 to go
ZofBot Zoffix, List parameters List parameters capture a variable length list of data
lizmat continues on the P6W 22:08
AlexDaniel Zoffix: well, if I used the search function before submitting tickets more often, we'd be much closer to 0 ;)
lizmat wonders what she pushed to surprise SamCV 22:10
Zoffix "Dear zoffix, [...] As one of r/programming's most prolific contributors, we'd like to talk to you! Between January '16 and April '17, you posted 22 times on Reddit's r/programming (putting you at rank 169 out of 14,254 users who posted on r/programming, i.e., the top 2%)" 22:25
top 2% posters? Color me dubious
ZofBot: when I said I wanted to be the top-2-percenter, I meant money, not posts! 22:28
ZofBot Zoffix, github didn't realize the file was totally deleted so viewing the diff looks terrible heh
lizmat and another Perl 6 Weekly hits the Net: p6weekly.wordpress.com/2017/07/17/...-released/ 23:28