<r0ssi>
after i upgrade to ruby 2.5, cinch will now reply with the first line, as expected, but the second line seems to get queued somewhere and never writes to the channel
<r0ssi>
instead, if the !brew command (or any other command, actually [eg !gis]) is issued again, cinch will output the ORIGINAL second line, then the first line of the new query
<leftylink>
mmm, yes, I saw that behaviour in various Ruby versions as well, though I've by now forgotten which versions do and do not exhibit the behaviour. it looks like last time this was mentioned in this channel was https://freenode.irclog.whitequark.org/cinch/2018-09-20 .
<r0ssi>
ok, at least i know i'm not going crazy
<r0ssi>
i upgraded from ruby 1.9.3, so there's a whole helluva lot of version in between that might work :)
<r0ssi>
i'm pretty green with coding, so diving into the guts of cinch is a bit above my ability, but i can at least start to dig around and see if i can figure it out or at least narrow down if its a ruby version issue or whatever
<dominikh>
Cinch's threading and queuing is disgusting.
Azure has joined #cinch
<r0ssi>
not ideal, but a quick workaround that seems to work is to just put a sleep(1) between them