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

commandhandler error after updated the library to the 8.1.0 #871

Closed
91DarioDev opened this Issue Oct 15, 2017 · 5 comments

Comments

Projects
None yet
3 participants
@91DarioDev

91DarioDev commented Oct 15, 2017

after i updated the library to 8.1.0 i keep getting this error

 ERROR - An uncaught error was raised while processing the update
Traceback (most recent call last):
  File "/usr/local/lib/python3.5/dist-packages/telegram/ext/dispatcher.py", line 269, in process_update
    for handler in (x for x in self.handlers[group] if x.check_update(update)):
  File "/usr/local/lib/python3.5/dist-packages/telegram/ext/dispatcher.py", line 269, in <genexpr>
    for handler in (x for x in self.handlers[group] if x.check_update(update)):
  File "/usr/local/lib/python3.5/dist-packages/telegram/ext/commandhandler.py", line 137, in check_update
    command = message.text[1:].split(None, 1)[0].split('@')

i did not change a single line of my code and in fact reverting to the previous version of the library i am fine

edit:

steps to reproduce:

  • send a text message containing only one word.

it doesn't happen with commands or text containing more than one words or media

edit2:
set the log on DEBUG it also say
IndexError: list index out of range in addition to the previous Traceback

@91DarioDev

This comment has been minimized.

Show comment
Hide comment
@91DarioDev

91DarioDev commented Oct 15, 2017

i guess the issue could depend on this ec9b16a#diff-9cd44b48f0b3c83abd861dfd18b28090R137

@91DarioDev 91DarioDev changed the title from error after updated the library to the 8.1.0 to commandhandler error after updated the library to the 8.1.0 Oct 15, 2017

@jh0ker

This comment has been minimized.

Show comment
Hide comment
@jh0ker

jh0ker Oct 15, 2017

Member

@91DarioDev Do you mean one word or one character?

Member

jh0ker commented Oct 15, 2017

@91DarioDev Do you mean one word or one character?

@SitiSchu

This comment has been minimized.

Show comment
Hide comment
@SitiSchu

SitiSchu Oct 15, 2017

Contributor

I can confirm that this happens when you only send one character to the bot.

Contributor

SitiSchu commented Oct 15, 2017

I can confirm that this happens when you only send one character to the bot.

@SitiSchu

This comment has been minimized.

Show comment
Hide comment
@SitiSchu

SitiSchu Oct 15, 2017

Contributor

This can be tested with the echobot2.py example.

Contributor

SitiSchu commented Oct 15, 2017

This can be tested with the echobot2.py example.

@91DarioDev

This comment has been minimized.

Show comment
Hide comment
@91DarioDev

91DarioDev Oct 15, 2017

@jh0ker yes only one char. it is more than 1 char it's fine. sorry

91DarioDev commented Oct 15, 2017

@jh0ker yes only one char. it is more than 1 char it's fine. sorry

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment