<sabfer>
hi, I'm trying to get cinch to work with a hector irc server, but keep getting `parse_channel': undefined method `[]' for nil:NilClass. Any ideas?
<dominikh>
"Hector supports a limited subset of IRC commands" will probably be reason #1. give me an address I can connect to and I'll tell you where exactly it's screwing up
<dominikh>
actually, also show me your code
<sabfer>
address is not public since it's a company channel
<CM-Punk>
There's nothing that I can just code into the bot to keep it from responding to one person too many times?
<sabfer>
dominikh: hector attempts to be irc-compatible. cinch code is one of the standard cinch examples, but with password protected server and ssl on
<dominikh>
CM-Punk: you can code whatever you want in ruby. just store when/how often the person last spoke and choose not to respond
<dominikh>
sabfer: well, I'll need something to connect to so I can test it, and I'm not sure I feel inclined to install something for that
<sabfer>
dominikh: i'm willing to contribute a patch, but i'm still trying to find out why it fails. Does cinch expect a specially formatted motd?
<dominikh>
a bit confused myself there
<dominikh>
looks like it's a bug in Cinch that never got triggered before
<dominikh>
which… surprises me greatly
<sabfer>
dominikh: need help? want to create a github issue and continue the discussion there?
<dominikh>
nah. I can see why it fails, I'm wondering why it never failed before ;) after that the fix should be straightforward
<dominikh>
actually might be a bug in hector though
<sabfer>
let me know how can I help
<dominikh>
no worries.
<dominikh>
technically, Hector shouldn't be sending ":myserver.irc 422 :MOTD File is missing" but ":myserver.irc 422 ournick :MOTD File is missing"
<dominikh>
but meh, I'll fix it in Cinch instead
mpapis has quit [Quit: Goodbye]
<dominikh>
sabfer: for what it is worth, Cinch will not work if you don't set the MOTD either way. even if we get rid of the exception, it will just sit there and wait. the IRC registration process is completed when the client receives the messages 001..004 – Hector seems to stop after 001 if there's no MOTD
<dominikh>
also, how does one set the MOTD with Hector? :)
<sabfer>
dominikh: I see. Looks like there is no way to set the MOTD with Hector
<dominikh>
sabfer: fwiw, some other clients, weechat for example, will not work correctly, either.
<dominikh>
so that's the sort of thing you want to file as a bug on Hector I'm afraid. they need to send the messages 001 through 004
<dominikh>
https://bugs.kde.org/show_bug.cgi?id=292289 not the first person to have problems with their 422. admittedly, they chose to treat 422 like it replaces 002..004, but still…
<Cinchy>
[URL] Bug 292289 – Konversation does not auto-join channels when connecting to Hector IRC server
<dominikh>
I can add that workaround just as well, but I'm not sure what else will break down the line
<sabfer>
dominikh: thanks! I'll file a bug report on hector then. I don't know much about the IRC protocol, but looks easy to fix and submit a pull request too
<dominikh>
sabfer: I'll create a branch for Cinch in a second, you can build a gem from that if you want. it should work fine unless you run into more Hector bugs
<dominikh>
sabfer: pushed it to github. the branch is called fix/hector. build a gem from that if you want to give it a try
<sabfer>
dominikh: great, thanks! I'll give it a try
<dominikh>
(if it works fine, it'll be merged into the next maintenance release, too)
<sabfer>
dominikh: works perfectly.
<dominikh>
cool
<sabfer>
I have to leave now. Thanks again for all your help.
<dominikh>
you're welcome
sabfer has quit [Remote host closed the connection]
sabfer has joined #cinch
sabfer has quit [Remote host closed the connection]