Repository navigation
Different exception title [anyio 4.0] #2343
Description
Activity
This issue was resolved after I downgraded
anyiofrom4.0.0to3.7.1Reacted by Anton Rudnikov and Ivana KellyerI think Sentry should probably handle these in a nicer way
Reacted by Tobias Jacobowitz, Noel Lynagh, Vladimir Shkoda, Tara Tripathy, Kyle Holzinger and Maciej KaszkowiakI agree with @rushilsrivastava
Downgradinganyiomay mitigate this issue at hand, but its not a good solution. Sentry should be able to work with the new anyio versionsReacted by Ben Saufley, Gus Matias, Kyle Holzinger and Bruno Gelb@NullOsama could you please re-open the issue?
Reacted by Vladimir Shkoda, Tobias Jacobowitz, Tara Tripathy, Noel Lynagh, Lars van der Bijl, Ramos Choi, Ben Saufley, Kyle Holzinger and Bruno GelbI saw the same when updating to anyio 4. This could still be handled a lot better by Sentry. It's very difficult to find the main error in this output.
Hi @rushilsrivastava, @jacobowitz, @b0g3r, @nickderobertis, are any of you still observing this issue? If so, I will gladly reopen it 🙂
are any of you still observing this issue? If so, I will gladly reopen it 🙂
Yes, this still happens on newer version of
anyioReacted by Daniel Szoke- changed the title
[-]Different exception title[/-][+]Different exception title [anyio 4.0][/+]on Jun 7, 2024 27 remaining items
- moved this from Waiting for: Product Owner to No status in GitHub Issues with 👀 3
on Jun 28, 2024 Hello, a bit more context for Sentry devs :
I get this:
Note the absence of a stack trace on the
ZeroDivisionError- I barely even see it mentioned.I would expect something more like the following (see "spoiler" tag after code block) - except ideally with
handledset tofalse- the reason it's true here is because I manually calledsentry_sdk.capture_exception()from a artificial/unwanted global try/except block, ietry: await super().async_run('trio') except Exception: sentry_sdk.capture_exception() raise
The result:
Thanks in advance! :-)
EDIT: I had already seen getsentry/sentry#37716 which gave me hope in the first place, but no cigar - my versions should be OK - the issue says « It will also be included in the next Sentry Self-Hosted release (23.6.0, est. June 2023). » , and my versions are as follow (although note I'm not entirely done upgrading my server yet, I stopped at the last hard stop):
So Python
sentry-sdk2.27.0, self-hosted Sentry24.8.0.This problem should be fixed by #4164. However, since this change affects how issues are grouped in Sentry, it is a breaking change, and so it will only be released in the next major (
3.0.0).We plan to release an alpha version of
3.0.0soon (hopefully this week or next). There is no timeline yet for when we will release a stable version.Reacted by CheatermanReacted by CheatermanThanks a lot for your answer! Can't wait to see it with my own eyes :-) godspeed Sentry team & contributors!
How do you use Sentry?
Sentry Saas (sentry.io)
Version
1.29.2
Steps to Reproduce
I'm not sure if it's something I did recently but the errors started to all have the same generic title
ExceptionGroupunhandled errors in a TaskGroup
Expected Result
The way I expected the error to be shown is how it was before as shown in the following screenshots.
Actual Result
The previous screenshot shows how is the exception shown which is very different from what it was before and it doesn't show specific information about the actual error. BTW, these screenshots are of the same error but something happened that made it look like the later pic.