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
@simonvorobjev It's impossible to stop the async running handler from the timeout job. We've modified a few things more in ConversationHandler, but what it boils down to is that @run_async-callbacks that take a long time in combination with a ConversationHandler is not ideal.
Basically it is what it is, changing it is near impossible (you would have to determine which thread is running the specific callback and terminate that thread, which can't be done when it's blocking).
Hope you can agree that using @run_async decorated callbacks in a ConversationHandler is just a pain we'll have to deal with.
I'm closing this issue for now, but if you want to share some more light on it, feel free to respond and we might re-open
Steps to reproduce
Expected behaviour
Timeout job should be deleted in case of ConversationHandler.END and not be triggered
Actual behaviour
In this test after message "end!" message "timeout!" also will be triggered
Configuration
Windows 7
python-telegram-bot 11.1.0
certifi 2018.08.24
future 0.16.0
Python 3.7.0 (v3.7.0:1bf9cc5093, Jun 27 2018, 04:06:47) [MSC v.1914 32 bit (Intel)]
Logs
Simon, [09.10.18 11:04]
/begin
YoutuBot, [09.10.18 11:04]
start!
Simon, [09.10.18 11:04]
test
YoutuBot, [09.10.18 11:04]
end!
YoutuBot, [09.10.18 11:05]
timeout!
Simon, [09.10.18 21:50]
/begin
YoutuBot, [09.10.18 21:50]
begin!
YoutuBot, [09.10.18 21:50]
timeout!
The text was updated successfully, but these errors were encountered: