Don't log exception traceback on Forbidden for welcomes.#772
Merged
Conversation
sco1
approved these changes
Feb 23, 2020
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.
Closes #763.
Description
Members have a welcome DM sent to them on accepting rules, which may raise a
discord.Forbiddenexception in the case they have DMs disabled in their privacy settings.The current implementation catches a broad Exception and uses log.exception to allow the error to be logged fully with traceback as an exception without interrupting the code.
This is an unnecessary log since it's something by design, not an error, and the broad Exception catching is against the more explicit exception catching we prefer.
Changes
The
exceptblock only catchesdiscord.Forbiddenfor the single known case we're intending to handle and suppress.To ensure the original accept command message is still removed, it's placed in a
finallyblock. This allows unknown errors to raise correctly and propagate to the appropriate error logging and handling.