-
Notifications
You must be signed in to change notification settings - Fork 509
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
Sentry sdk causes requests to return an empty response when using graphql query #2285
Comments
Hey @reinoldus, thanks for the report! Please downgrade to 1.28.1 for now, we're working on a fix. |
1.29.1 released now that should fix the issue. |
Now we get a different issue with 1.29.1: (using sgqlc library)
|
@lpfann Thanks for reporting, looking into it. (In the meantime, downgrading to 1.28.1 will get rid of the issue.) |
We're also seeing the same set of issues. Downgrading to 1.28.1 seems to fix for now. |
@lpfann Having trouble reproducing this -- anything specific about your setup? Maybe a small code sample? |
We are using this is a rough snippet of the code that is causing this issue import requests query_str = """""" reqsession = requests.Session() |
Thanks a lot @MattLJoslin! This will help. I'll revert the feature that caused this for now so that more folks don't run into issues -- we'll revisit it later. Really sorry for the issues this caused. |
1.29.2 is now out and will get you all the good stuff from 1.29.0 without the GraphQL issues. |
Thanks for the quick responses! We are still looking forward to this feature since we almost exclusively use graphql in our services, but appreciate the rollback :) |
How do you use Sentry?
Cloud
Version
1.29.0
python version: 3.9
Steps to Reproduce
if you run the snippet above the response.content will come back as "", where if you run this:
The response comes back as expected.
I am running the query against a hasura instance, but I assume it has something to do with this new feature, so I assume all requests to all graphql servers are affected:
Pip freeze:
Downgrading to 1.28.1 fixes the issue
Expected Result
Populated "text" field in requests response object
Actual Result
The response is "stuck" in the raw HTTPResponse from urllib3
The text was updated successfully, but these errors were encountered: