New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feedback_email management command needs better exception handling #3356
Comments
@rjsparks@nostrum.com changed status from |
@jennifer@painless-security.com commented On #3357, email to settings.ADMINS was requested. Should the admins be contacted for this one, either instead of or alongside the nomcom chair? |
@rjsparks@nostrum.com commented No - only the nomcom chair should get this one. These messages have confidential content that the admins should not see. |
@jennifer@painless-security.com changed status from |
@jennifer@painless-security.com set owner to |
@jennifer@painless-security.com changed status from |
@jennifer@painless-security.com set resolution to |
@jennifer@painless-security.com commented Fixed in 968b775: Create management command base class that sends emails on exceptions. Fixes #3356 and #3357. Commit ready for merge. |
@rjsparks@nostrum.com commented Fixed in d9dc4f5: Merged in 968b775 from jennifer@painless-security.com: |
owner:jennifer@painless-security.com
resolution_fixed
type_defect
| by rjsparks@nostrum.comWe have at least one instance of an email crashing the feedback_email command in a way that causes them to get a bounce from the mail system that looks like:
This should not fail this way - if we can't recover enough to let the automated ingestion succeed it would be better to wrap the exception into something that gets sent (including the original message) to the nomcom chair.
Issue migrated from trac:3356 at 2022-03-04 09:08:46 +0000
The text was updated successfully, but these errors were encountered: