Ticket #1285 (assigned enhancement)

Opened 3 years ago

Last modified 2 years ago

Errors cause emails

Reported by: dread Owned by:
Priority: minor Milestone: ckan-future
Component: ckan Keywords:
Cc: Repository: ckan
Theme: none


Currently a sysadmin gets an email when an exception is not caught. But there are occasions when we DO want to catch an exception so we can fail nicely for the user, but the sysadmin STILL gets an email to know to fix something. e.g. if there is an exception when search indexes a package. You want to catch the exception and still run any other notify calls.

Change History

comment:1 Changed 3 years ago by dread

Another instance is when the database tables are not created and you want to both display a sensible error and have an email alert. #1290

comment:2 Changed 2 years ago by thejimmyg

  • Owner set to thejimmyg
  • Status changed from new to assigned

I could write some middleware to handle this. Can we come up with a list of exceptions not to catch or should I create a base exception called "NoEmailReportTriggeredException?()" which exceptions for this purpose have to be derived from or which code has to raise?

comment:3 Changed 2 years ago by dread

Isn't the point is we don't to raise an exception at all - we want to call a method to send the email and then return from the controller a normal html page. Don't we just need a method to get the error email address from the config and send an email.

comment:4 Changed 2 years ago by ross

  • Owner thejimmyg deleted
  • Milestone set to ckan-future
Note: See TracTickets for help on using tickets.