[Crash] except other Telegram API error codes #42
Labels
No Milestone
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: juergen/ticketfrei#42
Loading…
Reference in New Issue
There is no content yet.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may exist for a short time before cleaning up, in most cases it CANNOT be undone. Continue?
Author: @b3yond Posted at: 06.10.2018 07:06
The bot crashed with this traceback:
sometimes the Telegram API returns an error code as an integer. update is something like 404 in this case. Yet, we only except the error code 404, which Telegram also uses for bad auth. I thought they were too lazy to use different ones. But probably we just ran in another error code. a shame that it isn't included in the traceback.
@git-sid
Author: @b3yond Posted at: 06.10.2018 07:10
Here is a list of Telegram API return error codes: https://core.telegram.org/api/errors
we could think about all those error codes and implement them correctly, or just look if update is an integer and return an empy mentions list.
Author: @b3yond Posted at: 07.10.2018 17:10
This can not really be tested - we don't control the Telegram API. At least, when new error codes appear, they are logged now.