IRC channel logs
2019-08-07.log
back to list of logs
***Server sets mode: +nt
<manumanumanu>mapping test1 and test2 over (iota 10000000) yields a 2s difference in favor of test1 <wingo>the iota difference could be gc-related <wingo>pretty sure that benchmark is gc-dominated <wingo>iota makes a list tho, so does map <wingo>and it's a bit of a pathological case for gc (a 1e8 serial data structure) <manumanumanu>running it a couple of times changed it.. Sorry for wasting your time. <daviid>wingo: I was asking you because it needs, all it needs, is a channel admin to invite a bot - /invite globbot - that's all it takes, then we have good logs again <rekado>daviid: we now have bayfront-log. <rekado>I’ll also get the past logs from the gnunet folks. <rekado>I’ll update logs.guix.gnu.org in a few days to also display the #guile logs <daviid>rekado: it seems to me, with all due respect, and to save all of us some time, that this https://freenode.logbot.info/ is a better solution, immediat, a single command, and offers better display to <daviid>i was gona suggest you do that for #guix actually, so should #scheme, #kawa ... <karlosz>im curious on whether anyone has a retrospective on how well cps soup has worked as the guile ir so far <karlosz>seems like everyone just reaches for ssa nowadays, so it would be cool to see what kind of concrete advantages over ssa have shown up <rekado>daviid: I see no need to switch to something else for logging on #guix. It’s also just fine for us to have the logs on our own servers and to have a viewer that we can hack. <daviid>rekado: sure, but we haven't done anything to solve this problem, #guile i mean, for about almost two years now, and an admin can type '/invite globbot', and that's it, solved. then, when we have solced our own servers, logs, i won't, but if someone wants to, fine, we can kick globbot, ans tah's it ... <rekado>that’s not going to make the old logs available. <rekado>I’m getting those from the people who ran the old logger. <daviid>rekado: but it will start to log now, in one command, then we can work on ... and later kick the bot out ... <daviid>anyway, that's what i would do, right now <rekado>daviid: bayfront-log is already logging right now. <rekado>as soon as I get the old logs I’ll add them. <daviid>ah, thanks! why on earth didn't we know about this? very cool <daviid>we should make this available in our channel message, please ... <rekado>it only exists since … 3 minutes <rekado>when the issue of logs was brought up above I thought it shouldn’t be hard to fix it … finally. <rekado>later this week I might move this to logs.guix.gnu.org; we’ll see <daviid>dsmith-work: is it 'bot: one-word is ...' or can it be several words? *daviid is a complete bot ignorant <dsmith-work>daviid: And unfortuatnely, sometimes the bot see a word and thinks it's being addressed. <dsmith-work>And you get "some really really long description of something" is "done" <dsmith-work>daviid: I need to fix it so it only recognizes it's exact nick. <daviid>ah ok, i'll try to remeber that, and use it ... let's see :) <dsmith-work>daviid: ask the bot for help. (notice how I'm always avoiding using it's nick...) <daviid>dsmith-work: will do, yes i was also avoinding its nick when i did ask you ... :) <dsmith-work>I guess it's useful when someone is /ignore'ing you. You can have the bot deliver you message for you? <daviid>have to go, bbl, and read our new logs aha!! nobody will be able to write in my back anymore :):) just joking of course <sneek>daviid, dsmith-work says: logs