confirm processed message in examples#43
Merged
leandrotoledo merged 1 commit intopython-telegram-bot:masterfrom Aug 20, 2015
rahiel:master
Merged
confirm processed message in examples#43leandrotoledo merged 1 commit intopython-telegram-bot:masterfrom rahiel:master
leandrotoledo merged 1 commit intopython-telegram-bot:masterfrom
rahiel:master
Conversation
Member
|
Very well noted, thank you for your pull request. |
leandrotoledo
added a commit
that referenced
this pull request
Aug 20, 2015
confirm processed message in examples
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
You used that
if LAST_UPDATE_ID < update.update_idbecause .getUpdates sends updates from and includingLAST_UPDATE_ID, the last message that we already processed. Now it's one bigger so telegram considers the update as confirmed and doesn't resend it. (from the offset description)