sentry-laravel: Two Sentry issues for one exception
Ever since upgrading from 1.0.0-beta2 to 1.1.0 I am sometimes seeing two issues for a single exception, one prefaced with Notice:. This was one I created:
This could be happening every time, but I’m not sure as I am 2 days from launch. Is this from upgrading or something on my end?
At the time of upgrade I also stopped receiving emails for Laravel issues (but still get JS emails). I have checked my settings (that I didn’t ever change) and they look correct to alert me. Anyone else?
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Reactions: 3
- Comments: 23 (2 by maintainers)
sentry/sentry-laravel1.6.2was just released which fixes the regression causing duplicate exceptions, thanks all for the information and patience!Yes, as mentioned in #327 this problem is caused by
sentry/sentry:^2.3and will be fixed shortly for now pinning tosentry/sentry-laravel:1.5.*andsentry/sentry:2.2.*is a immediate fix if you need it.This issue was closed however I never mentioned we think it’s fixed in
1.4.0, please do open it back up or open a new issue if the problem is not solved.We are working on seeing if #280 solves the issue which is most likely the best “fix” for the issue without us missing issues (takes a bit of time to test).
Sentry registers it’s own error handler, which reports given error. And runs previous error handler after, which might throw an exception, like in Laravel HandleExceptions. That last exception is also reported by Sentry.
Guys, that’s because of Sentry’s integrations. They handle errors before laravel’s handler does it.