New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
_trigger_timeout() missing 1 required positional argument: 'job' #1366
Comments
It looks like we missed the _trigger_timeout callback when we went through the codebase updating to context based handlers. Thanks for the report, we'll get it fixed when we can :) |
I'm getting the same exception in version
This is how my conversation handler looks: from telegram.ext import CommandHandler, MessageHandler, ConversationHandler, Filters
ANY = range(1)
def start(update, context):
return ANY
def any(update, context):
pass
def cancel(update, context):
return ConversationHandler.END
def no_parse(update, context):
pass
def conversation_handler():
return ConversationHandler(
entry_points=[CommandHandler('tot', start)],
states={
ANY: [MessageHandler(
~Filters.command,
any
)]
},
fallbacks=[
CommandHandler('cancel', cancel),
MessageHandler(Filters.update, no_parse)
],
conversation_timeout=10
) |
Hello @felixlinker, i think this issue is still existent on the latest beta release which I first encountered it. Until the release is bumped, you can install the master branch so the latest changes are reflected. |
Steps to reproduce
ConversationalHandler
and useconversation_timeout=10
Expected behaviour
The conversation should timeout
Actual behaviour
From the chat, nothing happens. If i respond normally after the supposed timeout should have taken place, the bot responds to me as if no timeout has taken place.
Configuration
Operating System:
Version of Python, python-telegram-bot & dependencies:
Logs
The text was updated successfully, but these errors were encountered: