-
Notifications
You must be signed in to change notification settings - Fork 515
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
Weird behaviour after integrating Sentry SDK #3919
Comments
Hey @imeckr thanks for reporting this! Do you have a minimal reproduction of this? I found an issue that describes the same problem when using datadog: DataDog/dd-trace-py#6041 |
@antonpirker Thanks for sharing the relevant issue, it does seem like its caused by some quirk in the Python's ssl package. But I am not sure how to fix that. To answer your questions:
I am going to remove Sentry for a couple of days and see if the error persists, will report back after that. |
@imeckr I see you are using profiling, if possible could you also check without profiling ( |
How do you use Sentry?
Sentry Saas (sentry.io)
Version
2.19.2
Steps to Reproduce
I am not sure if its a Sentry issue but I started seeing this after we integrated sentry-sdk in to our FastAPI project.
This how we initialised the SDK
Now the issue is that my app has started throwing errors on certain auth endpoint (Firebase
id_token
verification), an SSL errorThe error suggests that somehow
len
which is a python keyword has been reassigned to an integer, which is very unexpected and means somehow it got polluted. I checked our project there is no such re-assignment. Curiously I searched forlen=
in thesentry-sdk
repo, and found this.sentry-python/sentry_sdk/serializer.py
Line 314 in 9f9ff34
This seems to be some internal function which would take sometime for me to understand. But can someone just double check this and tell if I am looking at the direction.
Expected Result
Should not get the above error.
Actual Result
The text was updated successfully, but these errors were encountered: