github.com/moarvm/moarvm | IRC logs at colabti.org/irclogger/irclogger_logs/moarvm
Set by AlexDaniel on 12 June 2018.
00:54 nativecallable6 joined, committable6 joined, shareable6 joined 00:55 quotable6 joined, coverable6 joined, reportable6 joined, benchable6 joined, greppable6 joined, releasable6 joined, statisfiable6 joined, bloatable6 joined 00:56 notable6 joined, squashable6 joined, unicodable6 joined 02:04 AlexDaniel joined, AlexDaniel left, AlexDaniel joined 05:05 benchable6 left, statisfiable6 left, bloatable6 left, committable6 left, unicodable6 left, coverable6 left, nativecallable6 left, greppable6 left, notable6 left, reportable6 left, releasable6 left, quotable6 left, squashable6 left, shareable6 left, committable6 joined, unicodable6 joined, nativecallable6 joined 05:06 shareable6 joined, quotable6 joined, releasable6 joined, bloatable6 joined, coverable6 joined, benchable6 joined 05:07 notable6 joined, greppable6 joined 05:08 reportable6 joined, statisfiable6 joined, squashable6 joined
nine This line actually looks more worrying: github.com/MoarVM/MoarVM/blob/mast...all.c#L576 07:56
^H^H^H^H^H^H^H^H^H^H^H^H^H^H^H^H^H^H^H^H^H^H^H^H^H^H^H^H^H^H^H^H^H^H^H^H^H^H^H^H^H^H^H^H^H^HOh, no it doesn't 07:57
lizmat teaser :-) 08:11
08:38 domidumont joined 08:49 sena_kun joined 08:52 domidumont left 09:04 robertle joined 09:07 Altai-man_ joined 09:10 sena_kun left 09:22 sena_kun joined 09:24 Altai-man_ left 10:10 sena_kun left 11:58 ZzZombo joined 13:01 MasterDuke left 13:15 MasterDuke joined 13:19 sena_kun joined
MasterDuke timotimo: i'm at HEAD of moarperf, but when i load a profile `perl6 -I lib service.p6 <path to .sqlite3>` it seems to load ok, but i just get `There is nothing at this URL. Return` when i open the link 13:20
13:22 Altai-man_ joined
MasterDuke somewhat related, but question for all. why would a profile show a method as not jitted at all, but the spesh log say it was jitted successfully? 13:22
13:25 sena_kun left
MasterDuke could a `# JIT: devirtualized` cause that? 13:33
13:37 lucasb joined
timotimo no that's a good thing 13:42
14:28 Geth joined
MasterDuke another question. why would a method have no interned callsites even though the statistics show a ton of hits for just one? 14:33
japhb MasterDuke: I'm having the same problem in moarperf as well (reported in this channel back on Friday). At the time timotimo thought it might be an implicit dependency that we're missing that he has installed (and thus doesn't notice). 14:42
MasterDuke i did get some warnings about peer dependencies during the `npm install .` phase. but i don't know anything about npm/js, so i just ignored them. maybe they were really relevant 14:43
timotimo they're pesky; on my machine it still all works >_> 14:49
MasterDuke it did work as of a little while ago 14:50
14:50 robertle left
MasterDuke but i couldn't say exactly which commit 14:51
npm WARN @babel/plugin-transform-async-to-generator@7.0.0-beta.53 requires a peer of @babel/core@>=7.0.0-beta.50 <7.0.0-rc.0 but none is installed. You must install peer dependencies yourself. 15:03
npm WARN @babel/preset-es2017@7.0.0-beta.53 requires a peer of @babel/core@>=7.0.0-beta.50 <7.0.0-rc.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email@hidden.address] requires a peer of popper.js@^1.14.7 but none is installed. You must install peer dependencies yourself.
npm WARN [email@hidden.address] No repository field. 15:04
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email@hidden.address] (node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for [email@hidden.address] wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
whoops, more text than i expected, probably should have just created an issue 15:05
github.com/timo/moarperf/issues/6 15:08
timotimo fsevents is skipped because it's not needed on linux 15:11
MasterDuke yeah, that one didn't seem likely to be a problem 15:14
15:23 sena_kun joined, sena_kun left 15:24 Altai-man_ left
timotimo MasterDuke, japhb, can you tell me what "npm run dev" tells you? 15:29
i have travis-ci doing builds of moarperf and it's working just fine there
MasterDuke timotimo: in frontend? 15:30
timotimo yes
15:32 robertle joined
MasterDuke takes so long... 15:32
timotimo: commented on the issue 15:35
timotimo yeah it takes a while
but that looks perfect
and even then it gives 404 or whatever it is when connecting? 15:36
what does the service.pm6 log say?
MasterDuke commented again 15:38
timotimo i don't see a 404 anywhere 15:41
japhb I'm not at that machine, so I can't `npm run dev`. But I can say it didn't 404; it just gives the error message that MasterDuke and I reported. It looks like the screen *should* have content (clearly it's using the normal CSS), but it just has the `There is nothing at this URL. Return` error, where the 'Return' bit is a link back to the home page. 15:45
MasterDuke `frontend/index.js:273: <Row><Col>There is nothing at this URL. <Link to="/">Return</Link></Col></Row>` 15:55
japhb twitches at the replaced HTML tags 16:00
timotimo oh 16:08
i did not know i had something like that in there, LOL
aha, looks like i changed that to just "oh no" locally 16:10
or revereted a change or something
what URL does it show you when you get that?
MasterDuke localhost:20000/#/prof/ 16:27
timotimo hm, ok, what moarperf commit are you on? 16:29
MasterDuke commit bfe3a2da952507d7000512edba051268d10838df (HEAD -> master, origin/master) 16:30
timotimo: mostly not related, but you can now change your `use v6.d.PREVIEW;` in service.p6 to `use v6.d;` 16:44
timotimo ah, indeed
17:24 sena_kun joined
lizmat and another Rakudo Weekly hits the Net: rakudoweekly.blog/2019/11/11/2019-45-red-alert/ 17:31
17:46 donaldh joined 18:14 donaldh left 18:15 donaldh joined 18:20 donaldh left 18:26 donaldh joined 18:31 donaldh left 18:38 Kaiepi joined 19:00 donaldh joined 19:05 donaldh left 19:22 Altai-man_ joined 19:24 sena_kun left 19:43 donaldh joined 19:47 donaldh left 19:55 donaldh joined 19:59 donaldh left 20:41 donaldh joined 21:03 Altai-man_ left 21:37 lucasb left 21:43 donaldh left

Powered by Cro and the Raku® Programming Language.

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

Thank you!