Closed Mapiarz closed 9 months ago
Hey @Mapiarz Thanks for reporting this. Yea, it looks like Django Debug Toolbar and Sentry are monkey patching the same functions and when Django Debug Toolbar is "unpatching" something an error is happening.
I put in on our backlog, but this has not a really big priority right now. But we are always happy about PRs when you want to try to fix this!
Hey @Mapiarz
Finally had time to look at this. I created a simple Django app with strawberry and django debug toolbar and made some requests to the /graphql
endpoint and everything works as expected.
The packege versions I used (only showing relevant ones, no dependencies):
Django==4.2.7
django-debug-toolbar==4.2.0
graphql-core==3.2.3
psycopg==3.1.12
strawberry-graphql==0.212.0
strawberry-graphql-django==0.24.0
sentry-sdk==1.34.0
Can you try to update your Sentry SDK version to the newest ones and also update Django Debug Toolbar? If it is still not working after updating all the libs to the newest versions, please supply a minimal project with that I can reproduce this.
This issue has gone three weeks without activity. In another week, I will close it.
But! If you comment or otherwise update it, I will reset the clock, and if you remove the label Waiting for: Community
, I will leave it alone ... forever!
"A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀
How do you use Sentry?
Sentry Saas (sentry.io)
Version
1.22.2
Steps to Reproduce
We have a django app which serves only to expose a single GraphQL endpoint. We are using Strawberry Django.
All queries will crash with both Django Debug Toolbar and Sentry enabled. If I disable sentry, all works. If I disable DDT, all works as well. Both enabled leads to all queries crashing in the same way.
Errors are correctly pushed to sentry.io, that's not a problem.
Expected Result
Queries should continue to work.
Actual Result
Queries don't work. Example:
Any ideas what could be happening? Some monkeypatching conflicts? Things to try or check?