dominikh changed the topic of #cinch to: The IRC Framework | Latest version: Cinch 2.3.1 | You're being logged at https://irclog.whitequark.org/cinch/
Miron has quit [Ping timeout: 265 seconds]
Miron has joined #cinch
Azure has quit [Read error: Connection reset by peer]
Azure has joined #cinch
w80 has joined #cinch
Azure has quit [Ping timeout: 268 seconds]
Azure has joined #cinch
Azure has quit [Max SendQ exceeded]
Azure has joined #cinch
td512 has quit [Ping timeout: 256 seconds]
td512 has joined #cinch
td512 has quit [Changing host]
td512 has joined #cinch
foamz has quit [Quit: ~]
foamz has joined #cinch
Chew has quit [Quit: ~]
Chew has joined #cinch
craysiii has quit [Quit: ~]
craysiii has joined #cinch
snapcase has quit [Remote host closed the connection]
snapcase has joined #cinch
<w80>
anyone have success running cinch via jruby? what little i could find via searches seems to send mixed messages
<bougyman>
Never tried.
<bougyman>
Have you tried?
<w80>
yes
<bougyman>
And?
<w80>
it runs, connects... but most threads won't finish until - i think - another thread starts up?
<w80>
i spent about 6 hours last night messing with it on two very different bots done in cinch. the newer one, actually refuses to connect... but i think that's an openssl issue
<bougyman>
weird.
<w80>
yeah, i sort of expected it just not to work at all. i wouldn't even care, but the command i'm working on speeds up about 400-600% when it has real threads via jruby
<w80>
i'm not 100% sure, since i'm pretty ignorant, but i think under jruby the threads will return on their own after timing out... but that's a barely educated guess