Perl 6 - the future is here, just unevenly distributed

IRC log for #perl6-toolchain, 2016-06-12

| Channels | #perl6-toolchain index | Today | | Search | Google Search | Plain-Text | summary

All times shown according to UTC.

Time Nick Message
00:02 lizmat joined #perl6-toolchain
01:48 ilbot3 joined #perl6-toolchain
01:48 Topic for #perl6-toolchain is now Fire is step THREE! | https://github.com/perl6/toolchain-bikeshed | Channel logs: http://irclog.perlgeek.de/perl6-toolchain/today | useful prior art: https://metacpan.org/pod/CPAN::Meta::Spec
07:44 domidumont joined #perl6-toolchain
07:48 domidumont joined #perl6-toolchain
10:14 FROGGS joined #perl6-toolchain
10:30 nine ugexe: I usually use this patch: https://gist.github.com/niner/c347b3fcf62a49b981a588d70f9154c7
10:30 nine ugexe: otherwise as you mentioned, debugging is much harder
10:39 domidumont joined #perl6-toolchain
15:00 ugexe https://github.com/rakudo/rakudo/compare/nom...ugexe:cur-updates?expand=1#diff-c97d8fc8b5978ba87f7f726ed9cc28a4R219
15:01 ugexe that lets the error debugging work
15:08 ugexe i've had to work around that `run` bug before: https://github.com/ugexe/zef/blob/master/lib/Zef/Client.pm6#L772 where it has to eagerly read :err first followed by :out, and then it also has to do `$ = $proc.out/err.close` or `|$proc.out/err.close` (otherwise it doesn't get sunk?)
15:15 ugexe RT#125757 is related i think
15:21 ribasushi joined #perl6-toolchain
15:24 ugexe and my guess is the `run` bug somehow causes an unlock to be missed and it gets stuck in a deadlock
15:51 domidumont joined #perl6-toolchain
18:55 edehont joined #perl6-toolchain
19:15 tbrowder joined #perl6-toolchain
20:16 TimToady joined #perl6-toolchain

| Channels | #perl6-toolchain index | Today | | Search | Google Search | Plain-Text | summary