-
Notifications
You must be signed in to change notification settings - Fork 20
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
use new FatalErrorWithLog #102
Labels
enhancement
update an existing command or cog for some new functionality
good first issue
Good for newcomers
Comments
andrewj-brown
added
enhancement
update an existing command or cog for some new functionality
good first issue
Good for newcomers
labels
Apr 25, 2023
andrewj-brown
changed the title
use new (to-be-merged) FatalErrorWithLog
use new FatalErrorWithLog
May 10, 2023
FatalErrorWithLog is now live (wahey!), but only used in Starboard (awww). |
Haiku detection now uses |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
enhancement
update an existing command or cog for some new functionality
good first issue
Good for newcomers
SB2.0 (#75) includes a brand-spanking-new exception, FatalErrorWithLog. Implemented as part of utils, it's an exception for bad internal states or other code-based failures. Importantly, the exception comes with a logging system that sends its exception message to #admin-alerts.
Because logging internal failures to #admin-alerts is significantly more useful than the existing Azure log trace, all the rest of UQCSBot's code should be reviewed for cases where FatalErrorWithLog should be used (or even extended by further custom exceptions) to log errors.
The text was updated successfully, but these errors were encountered: