Anton Pirker
Anton Pirker
Hey @vagi8 . Yea, we do not want to have code specifically for Django in `utils`. That is a no go. I guess we can just say, that we can...
Hey @vagi8 ! Wow, thanks for the PR! We will have a look at it. I can not promise any ETA yes, because right now PRs are kind of piling...
Hey @antoine-de! Thanks for writing in! We have no integrations for the low level psycopg lib but for higher level database access libs like Django ORM or SQLAlchemy or asyncpg....
As described in my comment above (https://github.com/getsentry/sentry-python/issues/2427#issuecomment-1757302951) we do not need a dedicated psycopg3 integrations, because we hook into sqlalchemy and django. So please do not create an integration @vagi8...
Yes for the case that you do not use SQLAlchemy or Django a distinct integration would be useful. I just meant if you use SQLAlchemy or Django, then psycopg3 should...
Hey @bruno-gelb ! I just removed all our milestones because we kind of did not use them the correct way. There has been no change in priority for this, we...
tl;dr for this issue: 1) With `anyio` version `4.0.0` anyio is using [Pythons ExceptionGroups](https://docs.python.org/3/library/exceptions.html#exception-groups) instead of a custom exception group implementation they used earlier. 2) Sentry handles exception groups different...
## Gathering feedback To everyone in the thread (also the ones that only "thumb up" on comments: 1) Can you find your error in the exception group? 2) How can...
This is a problem in the Python SDK. The `sample_rate` in the envelope headers of an error is indeed a `float` instead of a `str`. (for envelopes containing transactions it...
This issue is related to some other issues (I tagged all of them with the "Integration: Logging" label) I put it in the internal backlog with low priority. Any help...