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
Icepeak logs errors to Sentry in case an exception occurs (see #52). It would be nice to see a number of tests that verify this functionality. These tests would somehow cause Icepeak to crash deliberately and verify that the correct errors are send to the Sentry DSN that is specified, for example by inspecting the records that are send from Icepeak. It should not be possible to let Icepeak crash when in production.
The text was updated successfully, but these errors were encountered:
Hi @NunoAlexandre, I was personally thinking about the module System.Log.Raven.Transport.Debug of the raven-haskell package we use for Icepeak. This would allow us to swap out the destination where Sentry would sent error messages, which we could then inspect.
Icepeak logs errors to Sentry in case an exception occurs (see #52). It would be nice to see a number of tests that verify this functionality. These tests would somehow cause Icepeak to crash deliberately and verify that the correct errors are send to the Sentry DSN that is specified, for example by inspecting the records that are send from Icepeak. It should not be possible to let Icepeak crash when in production.
The text was updated successfully, but these errors were encountered: