Server Timeout makes ther listener to crash #7
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.
The mastodon streaming listener may enter into a Server's TimeOut. The wrapper then fails with an Exception and this escalates up until the app. At this point the MastoFeed listener restarts.
More than a big error, it is a normal behavior due to the server timeout. The logging should become less severe.
In this step the idea is to handle the exception and log it as a smaller error, still sending the Janitor notification (to ensure we identify the exception correctly). In a further step it should just avoid using Janitor.
currently, after notifying and logging, it restarts listening. this should continue.
Traceback: