<Cinchy_>
[gist] bot.rb (at gist.github.com, britishtea on 2013-11-24 16:55)
<dominikh>
uh, there's an exception
<waxjar>
yeah. i can't catch, though. any idea on how to fix it?
<dominikh>
eh, it's a bug in Cinch. one I thought I had fixed a while ago
<dominikh>
apparently not
<waxjar>
ah.
<dominikh>
not quite sure why it's happening though :D
<dominikh>
also it's working locally
<waxjar>
hmm. is that HEAD?
<dominikh>
I tested with 2.0.10
<dominikh>
oh, hold on
<dominikh>
what IRC server are you testing that on?
<dominikh>
rather, what server software
<waxjar>
inspircd
<dominikh>
(it works here because it's using a different code path)
<waxjar>
version 2.0.13 r0
<dominikh>
freenode sends a 402, not a 401 :)
<dominikh>
got a public server for me to test on? :>
<waxjar>
irc.what-network.com is where i originally ran into it
<dominikh>
there we go.
<DeepBlue>
well,where 2 get more scripts?
<dominikh>
write them.
<DeepBlue>
dominikh: can i load tcl scripts?
<dominikh>
no.
<dominikh>
waxjar: build from the latest maint branch (that I just pushed) and see if that fixes the issue and doesn't break anything else.
<waxjar>
dominikh: that works wonderfully!
<dominikh>
if it doesn't break anything else I'll release a .11 :)
<waxjar>
sahweet :D
<dominikh>
hm. I remember fixing something else for someone and waiting for feedback, but I forgot what that was…
<dominikh>
or who that was
<dominikh>
ah, that was qb
<dominikh>
qb: noticed any issues with the custom branch with the fix (user hosts, rizon, etc)?
<qb>
nothing is broken as far as I can tell
<qb>
but it still gets hit with the whois limiting rizon does
<dominikh>
but it shouldn't need a whois to get the host anymore
<qb>
yeah that part works as intended
<qb>
I was wrong in what was causing my issue
<dominikh>
okay, great. as for rizon being braindead… I'll have to work around that one day
<qb>
as far as I can tell they don't limit /who
<qb>
just /whois
<dominikh>
yeah, whois tends to be a more expensive operation
<qb>
but /who seems to have a different response on freenode versus rizon
<dominikh>
the format of WHO replies are standardized. if the server supports WHOX, however, we use WHOX with a specific format
<dominikh>
we don't use WHO/WHOX often though, only when the bot joins a channel.
<qb>
for rizon I get Hr 0 versus H 0 here
<qb>
the r means identified, correct?
<dominikh>
I have no idea; ask the idiot who thought modifying a standard reply was okay. it doesn't matter though, we don't use that part of the reply
Spami has joined #cinch
robonerd has joined #cinch
robonerd has quit [Changing host]
robonerd has joined #cinch
robonerd has quit [Client Quit]
postmodern has joined #cinch
DeepBlue has quit [Read error: Connection reset by peer]
DeepBlue has joined #cinch
DeepBlue has quit [Ping timeout: 272 seconds]
DeepBlue has joined #cinch
Spami has quit [Quit: This computer has gone to sleep]
Naski has joined #cinch
<Naski>
Hi all, I'm trying to create a basic word counter for every user in channel. Problem is that my code isn't thread-safe and it crashes as soon as there is little more activity. I know that I should use the synchronize-method, but I didn't quite understand that what I need to do from the documentation
<Naski>
http://pastebin.com/MxFxFtQW added the syncronize blocks, but it still starts to create concurrent threads under heavy usage
swingha has joined #cinch
<dominikh>
non-concurrent threads would quite be something. and both methods will need to synchronize on the same symbol, otherwise those two will race.
<dominikh>
(or use a proper database/orm that will do that for you)
<Naski>
heh meant that it starts to spawn new threads on the same action even though the old ones are still being completed
<Naski>
using postgres atm
<dominikh>
well, that's intended behaviour. every handler invocation happens in its own thread
<dominikh>
and naturally your handlers should be fast enough to not create an infinite backlog
<dominikh>
sorry, I'd help more, but I'm heading off to bed