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.
Unfortunately the current gem version of Cinch does not support Threads. We will soon be releasing version 1.0.0, which is likely to provide backwards incompatible changes, but will support threading inside plugins, and a nice modular plugin interface.
See here and check out the merge branch of Cinch to see what the new version will support. It will most likely be released in the next couple of days. Before updating please be sure to re-configure your Cinch based bots.
To make things clear, we will not only support threading inside plugins, but plugins themselves will be executed in threads. Without any kind of timeout, though.
Imho, it's the responsibility of the plugin developer to take care of timeouts, especially because it will not hurt if a plugin call takes forever since they will be running concurrently, anyway.
it can fail if you use threads in plugins.
actually I think plugins(rules) should be executed in threads and maybe allow to set a timeout option
something like
Timeout.timeout(timeout_option) do
Thread.start do
blk.call(...)
end
end
The text was updated successfully, but these errors were encountered: