06:50 <leftylink> hmm... I wonder if there's a way to determine whether the bot was successful in sending a message to a channel. I could look for any ERR_CANNOTSENDTOCHAN or something, but it's not certain I could know which message failed

06:50 <leftylink> hmmmmmmmmmmmmm

06:52 <leftylink> why do I care? oh iono, if I want the bot to respond to a command, but let's say the bot has a mute on it or the channel is +m or the bot got kicked before it could respond... then again you might ask "well shit, maybe they should use a different channel, that's not your problem to solve", and... maybe.

06:54 <leftylink> yeah I don't think I'm going to think too hard about this one. best-effort. and how much time do I want to spend into think about these silly cases? probably not that much

06:55 <leftylink> nevertheless if you can think of a general solution then... we could talk!

07:00 <leftylink> oh, the continuation of my thought would have been "so what if I want to say: if m.reply would fail, then just m.user.send the response"

07:01 <leftylink> but screw it, if people are using commands and the bot can't respond, that's not really my problem, I don't think

14:03 <tinnvec> leftylink: under what circumstances might the bot not be able to talk? perhaps there's another angle to attack this from. For instance if the channel is +m but the bot is not +v?

14:46 <dominikh> well, there's a quite simple issue here: if you send two messages at once, and get one error in return, you have no idea what message that error was for.

15:08 <tinnvec> ah, great point dominikh

16:53 <tinnvec> I'm extending the Cinch::Bot class for my bot, but am having trouble with testing.

16:53 <dominikh> testing Cinch, good one

16:53 <tinnvec> oh is that not done? lol

16:54 <dominikh> Cinch is an untestable mess.

16:54 <tinnvec> ah, well then maybe I'll just stick to testing my additions

16:55 <tinnvec> my bot class works just fine, just like the original, so if I can't test the original stuff, welp

16:56 <leftylink> yeah iono, sometimes I use https://github.com/bhaberer/cinch-test and I do have some successes with it (you can pretend to send a message and see all messages the bot sends to the sending user and/or the channel the message was sent on)

16:56 <leftylink> it is lacking in some of my uses that don't fit that pattern

16:56 <leftylink> testing timered things gets a bit funky, for example

16:57 <tinnvec> ah thanks leftylink, hadn't run accross that yet

16:58 <leftylink> "user 1 sends a message, an arbitrary channel gets a message in response" and "user 1 sends a message, an arbitrary user2 gets a message in response" are both cumbersome but still but doable with some uglyhacks

16:58 <leftylink> but on the whole I consider cinch-test better than nothing and I've used it to test my cinch bots, so

16:59 <leftylink> that's my cinch testing story

16:59 <tinnvec> haha thanks