github.com/moarvm/moarvm | IRC logs at colabti.org/irclogger/irclogger_logs/moarvm
Set by AlexDaniel on 12 June 2018.
dogbert17 where is everyone? 13:53
tadzik o/ 13:54
timotimo \o 13:55
dogbert17 hello
timotimo HELO
timotimo m: say uniname("???") 13:56
camelia QUESTION MARK
dogbert17 nice blogpost timotimo
timotimo thank you!
dogbert17 the stroopwafel had me confused for a bit :-) 13:57
never heard about it before
timotimo that may have been a little eurocentric 13:59
i should perhaps put a link or two for people unfamiliar with it
dogbert17 not on my behalf, japhb have already posted an answer :) 14:02
timotimo hm?
dogbert17 timotimo: colabti.org/irclogger/irclogger_lo...-10-25#l81 14:04
timotimo ah, i saw that!
dogbert17 is trying to understandt M#1208 14:11
synopsebot M#1208 [open]: github.com/MoarVM/MoarVM/issues/1208 [BLOCKER] Valgrind errors when running t/spec/S32-str/encode.t
dogbert17 oh, I think I know what the problem is 14:58
dogbert17 tests a patch 15:00
Geth_ MoarVM: dogbert17++ created pull request #1210:
Reset utf8 pointer to point at original string before using		 15:40
MoarVM: da19661e8f | (Jan-Olof Hendig)++ | src/strings/utf8.c
Reset utf8 pointer to point at original string before using

When an invalid utf8 sequence is found the original string is parsed again in order to figure out where in the string the problem occurs so that it will be possible to print out the bytes surrounding the error in the exception msg. The problem is that when trying to print out the bytes ... (6 more lines)		 15:57
MoarVM: aba68e41e2 | niner++ (committed using GitHub Web editor) | src/strings/utf8.c
Merge pull request #1210 from dogbert17/fix-m-1208

Reset utf8 pointer to point at original string before using
MoarVM: 48491b8969 | (Aleks-Daniel Jakimenko-Aleksejev)++ | src/strings/utf8.c
Make ut8_decode code just a bit easier to understand
 16:20
travis-ci MoarVM build failed. niner 'Merge pull request #1210 from dogbert17/fix-m-1208 16:38
travis-ci.org/MoarVM/MoarVM/builds/603980914 github.com/MoarVM/MoarVM/compare/0...a68e41e2d7
nine All failures are: Found /tmp/moar/bin/moar version 2019.07.1-308-gaba68e41e, which is too old. Wanted at least 2019.07.1-309-g48491b896 at /Users/travis/build/MoarVM/MoarVM/nqp/3rdparty/nqp-configure/lib/NQP/Config.pm line 190 16:55
nwc10 which is because travis is ignoring some of its configuration? Or because the configuration we give it is not "tight" enough? 16:59
timotimo that ususally happens when a bump was made at an unfortunate moment, i believe? 17:38
like, when you bump the moar requirement of nqp while travis still has a queue of moar builds to process 17:39
a bit of trickery could allow us to look for bump commits in nqp when doing the moarvm CI build and go back as far as necessary 17:44
Geth_ MoarVM: Kaiepi++ created pull request #1211:
Use more appropriate flags with getaddrinfo		 20:24
Kaiepi ^ can this be merged before the next release? it's the most important change from that pr, the others can wait 20:25
lizmat And yet another Rakudo Weekly hits the Net: rakudoweekly.blog/2019/10/28/2019-...e-toaling/ 20:49

Powered by Cro and the Raku® Programming Language.

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

Thank you!