IRC channel logs


back to list of logs

<dsmith-work>nckx: Part of me says Sure!
<dsmith-work>Looks like that channel has a small number of nicks in it. Like 20-30 ?
<dsmith-work>Ok, I'll add that chan. But please don't abuse the poor bot.
<dsmith-work>Not sure why it's not responding to !uptime
<nckx>If anyone abuses it I'll be very, very angry. And so will you I'm sure.
<nckx>sneek: !uptime
<nckx>It's weird. In PM, I get: -sneek- You need to supply a channel name for this command
<nckx>Adding one, silence.
<dsmith-work>nckx: Some (most?) "!" commands only respond to my nick.
<nckx>I expected that, which is why I didn't expect the usage error at all.
<nckx>sneek: ur sidechannel is leaking
<nckx>Better run after it.
<dsmith-work>The bot has a mix of commands. THe "!" style commands are from bobot++, the "botnick: ..." are from sarahbot
<stis>a vector of 10M random reals takes 16s on current guile to write to /dev/null. My implementation is now at 0.5s, that's 300-400MB/s
<stis>600-800MB/s are the current limit
<ArneBab>Is there a solution to make a module non-declarative (#:declarative? #f) and still be Guile 2.2 compatible?
<daviid>ArneBab: a solution(hack)( was proposed by dthomson, i snarfed it let me paste
<ArneBab>Thank you!?
<ArneBab>Thank you!
*ArneBab is sorry for the !? — has a metal safety on the finger right now that’s a bit wider than the keys.
<daviid> - line 35 - 60 as the code and an example
<ArneBab>oh — nice!
<daviid>you may thank David Thompson :) - the onlyproblem, but there is no other way, is that you'd have to add the hack in each and every module that needs it ...
<dsmith>sneek: botsnack
<sneek>I've been running for one month and 8 days
<sneek>This system has been up 5 weeks, 3 days, 33 minutes
<dsmith>sneek: botsnack
<sneek>I've been running for 53 seconds
<sneek>This system has been up 5 weeks, 3 days, 44 minutes
<dsmith>nckx: See if that is working..
<dsmith>nckx: Seems to be working
<ArneBab>daviid: that works completely — thank you! Now Guile 2.2 might still not be able to run the server, but dryads-wake now runs again in the commandline for Guile 2.2
<ArneBab>(I hit that problem yesterday because I worked on it from the presentation laptop with trisquel; updating Guile was not an option, because I had roughly one hour of battery time and I did not know how many other updates that would pull)
<ArneBab>wingo: good morning!
<ArneBab>wingo: would you accept a patch to Guile 2.2 that adds #:declarative? #f to define-module as ignored API compatibility setting?
<wingo>sure. no 2.2 releases planned tho, so it might be just as well to patch it downstream
<wingo>unless there is another reason to release 2.2.x
<ArneBab>Since the task for both is basically the same (provide a patch), I take that as a yes :-)
<ArneBab>main challenge: getting it right (so it will have to go through review in guile-devel to ensure that I don’t break stuff)
<nckx>dsmith-work: It does! Muchoes gracia's.
<dsmith-work>UGT Greetings, Guilers
<leth>I must've misunderstood someting, or missed something obvious. I was debugging parameters with fibers not working but in my tests i wrote i can't get this code to work I thought it would.
***w1gz_ is now known as w1gz