-
Notifications
You must be signed in to change notification settings - Fork 529
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
Falcon integration does not respect custom exception handlers #1362
Comments
thx for reporting @alexmic, if you want it fixed sooner, PRs always welcome! |
Hey @khuongduy354, you're looking for the sentry-python/sentry_sdk/client.py Line 263 in 3176dde
sentry-python/sentry_sdk/integrations/__init__.py Lines 38 to 45 in 3176dde
DidNotEnable exception if it fails to import the instrumented library and that tells this code that the library is not installed and the integration for it shouldn't be enabled.)
But please note that someone's already working on this issue. |
…eporting error (#2465) * Falcon checks actual HTTP status before reporting error * Only support custom error handlers on Falcon 3+ * Add Falcon 3.1 to tox.ini This change fixes an issue where the Falcon integration would report an error occurring in a Falcon request handler to Sentry, even though a Falcon custom event handler was handling the exception, causing an HTTP status other than 5xx to be returned. From now on, Falcon will inspect the HTTP status on the response before sending the associated error event to Sentry, and the error will only be reported if the response status is a 5xx status. Fixes GH-#1362
We have fixed this issue for Falcon versions 3.0 and above only. In case anyone encounters this same bug in an older Falcon version, please feel free to submit a new issue, referencing this one. |
How do you use Sentry?
Sentry Saas (sentry.io)
Version
1.5.6
Steps to Reproduce
Expected Result
The
marshmallow
exception should not have been reported to Sentry.Actual Result
The custom exception leads to a 4xx, not a 5xx, yet it is still reported as an unhandled error on Sentry.
The text was updated successfully, but these errors were encountered: