You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm running clockwork using clockwork lib/clock.rb and have a custom error_handler which reraises the exception in development, or quietly logs to Sentry.io in staging/production.
## Implement a custom error handler to track clockwork# error events into Sentry via Raven.#error_handlerdo |exception|
# Throw these direct in development so that we# can see and action them sooner.ifRails.env.development?# Raise the exception again.raiseexceptionelse# Log the error to Sentry via Raven.Raven.capture_exception(exception)endend
However, despite what the README suggests this doesn't appear to break/stop the process and display the error in the console, it instead just carries on quietly.
Any suggestions on how to work around this? Would ideally like error_handler to break things in development when hitting errors.
The text was updated successfully, but these errors were encountered:
I'm running clockwork using
clockwork lib/clock.rb
and have a custom error_handler which reraises the exception in development, or quietly logs to Sentry.io in staging/production.However, despite what the README suggests this doesn't appear to break/stop the process and display the error in the console, it instead just carries on quietly.
Any suggestions on how to work around this? Would ideally like error_handler to break things in development when hitting errors.
The text was updated successfully, but these errors were encountered: