dominikh changed the topic of #cinch to: The IRC Framework | Latest version: Cinch 2.2.5
cats has quit [Ping timeout: 272 seconds]
cats has joined #cinch
CM-Punk has joined #cinch
<CM-Punk> http://pastie.org/private/0bm0cuetjarsat5nwy5ida This is one of my plugins, for some reason it's not responding when someone says something in the channel, it's not doing anything, like it's not even loaded
Azure has quit [Ping timeout: 264 seconds]
Azure has joined #cinch
head8debian has quit [Read error: Connection reset by peer]
head8debian has joined #cinch
head8debian has quit [Ping timeout: 264 seconds]
head8debian has joined #cinch
head8deb1an has joined #cinch
head8debian has quit [Ping timeout: 256 seconds]
head8deb1an has quit [Client Quit]
head8debian has joined #cinch
head8debian has joined #cinch
<leftylink> CM-Punk: I'm 100% not sure of this, but does it have anything to do with not calling `super` in your `initialize`
Azure has quit [Read error: Connection reset by peer]
Azure has joined #cinch
postmodern has quit [Quit: Leaving]
sarkyniin has joined #cinch
apt-get_ has joined #cinch
sarkyniin has quit [Read error: Connection reset by peer]
sarkyniin has joined #cinch
apt-get_ has quit [Ping timeout: 276 seconds]
sarkyniin has quit [Ping timeout: 265 seconds]
sarkyniin has joined #cinch
_whitelogger has joined #cinch
<awkisopen> I'm on latest cinch. it would appear that calling user#authed? on a user when listening_to :leaving gets the bot stuck in a WHOIS loop
<awkisopen> is there a way to work around this or force it to somehow use the cache
<dominikh> :leaving really ought to be called :left, and you really can't ask anything about the user there
<dominikh> the user is gone, and when a user is gone, the cache gets invalidated
<awkisopen> in general there doesn't appear to be a timeout on whois if it fails
<dominikh> (there shouldn't be a loop though, it should give up the first time when the user wasn't found)
<dominikh> unless there's a bug in Cinch or you're running on some broken IRCd
<awkisopen> yeah I'm not positive how this is stuck in a loop
<awkisopen> I'm on snoonet so it could be the latter
<dominikh> which network?
<dominikh> ok. which IRCd do they run?
<awkisopen> checkin
<awkisopen> I'm honestly not sure. I can tell you that it gives a 401 in response to a failed whois
sarkyniin has quit [Ping timeout: 276 seconds]
<awkisopen> checking to make sure I haven't done anything stupid like put it in a loop myself somehow
<dominikh> it's not your fault
<dominikh> probably a Cinch bug, still checking
<dominikh> anyway, loop aside, you can't ask anything about the user in :leaving (or :quit, :kill etc)
<awkisopen> that's good to know
<awkisopen> I thought maybe it would have done a WHOWAS
<dominikh> I don't think WHOWAS even includes the auth name?
<awkisopen> hmm it might not. I'll just start keeping track of that manually
<dominikh> yeah, it's a Cinch bug
<awkisopen> can confirm it's not my code though, I just ran - yeah
<awkisopen> haha
<dominikh> the snoonet IRCd behaves a bit differently (but still conformingly) than the other IRCds, so freenode etc never triggered the bug
<awkisopen> thanks for the explanation, now I know how to fix how this behaves
<dominikh> http://sprunge.us/KSVW should fix it and hopefully not break anything else
<dominikh> pushed to master, will cut a new release in a couple days (if I can remember)
<dominikh> good night
<awkisopen> thanks so much!
postmodern has joined #cinch
sarkyniin has joined #cinch
head8debian has quit [Ping timeout: 264 seconds]
head8debian has joined #cinch
cats has quit [Ping timeout: 265 seconds]
cats has joined #cinch
sarkyniin has quit [Remote host closed the connection]