intercept ssl_read eof error in fetch_updates#329
Open
projecteurlumiere wants to merge 1 commit intoatipugin:masterfrom
Open
intercept ssl_read eof error in fetch_updates#329projecteurlumiere wants to merge 1 commit intoatipugin:masterfrom
projecteurlumiere wants to merge 1 commit intoatipugin:masterfrom
Conversation
1b6ea6c to
822f722
Compare
822f722 to
eb1ba6c
Compare
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
My bot has been encountering the following error once in every couple of days in the production environment:
While any API request can encounter this error, it's very annoying with
get_updatesbecause it kills the bot right away.I found out it's possible to configure OpenSSL to ignore unexpected eof errors - see docs for
SSL_OP_IGNORE_UNEXPECTED_EOFsetting. In the bot's case, however, the next retry always succeeds, so I presume it might be a genuine network error.Alternatively, this fix might belong at a lower level, not here. Yet, I've been using the most basic setup, and solving this problem turned up to be extremely frustrating as I really wasn't expecting
get_updatesto shut down like this.