-
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
Python 3.11.4 (and maybe others) break sentry-sdk's URL parsing that contains filtered elements #2160
Comments
sentrivana
added
Type: Bug
and removed
Status: Untriaged
Waiting for: Product Owner
labels
Jun 7, 2023
Thanks @hynek, we'll look at this right away. |
I suppose the quick fix would be changing sentry-python/sentry_sdk/utils.py Line 81 in 8a6c19c
|
Merged
This was referenced Jun 9, 2023
Merged
1 task
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
How do you use Sentry?
Sentry Saas (sentry.io)
Version
1.25.0 but tried older too
Steps to Reproduce
It looks like the recent security fixes to Python url parsing module broke
sentry_sdk.utils.parse_url()
which leads to baffling tracebacks e.g. when using the httpx integration & tracing.Internally
sentry_sdk.utils.parse_url()
uses a callurllib.parse.spliturl(url)
and as of 3.11.4, that explodes when that url includes[Filtered]
.I would expect this to be true for all Python versions that got a security update yesterday (3.10.12, 3.9.17, 3.8.17, 3.7.17, and 3.12.0 beta 2), but I have to run now, so I can't verify it.
Expected Result
sentry-sdk not exploding in baffling ways.
To be clear: this is kinda a big deal, because if I deploy an app that uses httpx and sentry on Python 3.11.4 (that's already in deadsnakes), the app will explode the first time it makes an http request.
Actual Result
3.11.3 works:
3.11.4 breaks:
The text was updated successfully, but these errors were encountered: