You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 13, 2019. It is now read-only.
I have cinch bots running on multiple networks and channels. I spawn a new thread for each bot I create per network. Many of those channels are getting very many channel messages. I have several on_channel handlers with regular expression:
on :channel, /.../ do |m, match1, match2 ... |
My last matchgroup would usually contain the rest of the message.
Quite often this last match group contains not only the remainder of the message, but also another messag efollowing right afterwards without any linebreaks separating the two.
For me this looks like a race condition and it makes it quite difficult to create some kind of show case. At least I can tell so far that I don't get any handler thread inflations which happen when my handlers were too slow.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I have cinch bots running on multiple networks and channels. I spawn a new thread for each bot I create per network. Many of those channels are getting very many channel messages. I have several on_channel handlers with regular expression:
on :channel, /.../ do |m, match1, match2 ... |
My last matchgroup would usually contain the rest of the message.
Quite often this last match group contains not only the remainder of the message, but also another messag efollowing right afterwards without any linebreaks separating the two.
For me this looks like a race condition and it makes it quite difficult to create some kind of show case. At least I can tell so far that I don't get any handler thread inflations which happen when my handlers were too slow.
The text was updated successfully, but these errors were encountered: