rollbar / pyrollbar

Error tracking and logging from Python to Rollbar
https://docs.rollbar.com/docs/python/
MIT License
213 stars 133 forks source link

Rollbar reporting ExceptionGroup instead of the raised exception #441

Open Niorlys opened 8 months ago

Niorlys commented 8 months ago

Expected Behaviour

When integrating Rollbar with FastAPI, I expected raised exceptions to be reported as they are: result.raise_for_status() This could raise HTTPError 502 Server Error: Bad Gateway for url:https://examplei.com

Actual

After the new update of Starlette, sometimes the traceback of an exception goes from exceptiongroup.ExceptionGroup: unhandled errors in a TaskGroup (1 sub-exception) to the original exception. It turns out that Rollbar is reporting the #59855 ExceptionGroup: unhandled errors in a TaskGroup (1 sub-exception) instead, obscuring the exception tracking in several cases.

I am using Python 3.10.8 and rollbar==0.16.3

danielmorell commented 8 months ago

Hey @Niorlys, thanks for sending us this!

Let me clarify to make sure I understand the desired behavior. You would like an ExceptionGroup that has a single sub-exception to be reported not as a group but as the sub-exception? Is that correct? I think that is a reasonable behavior, but I want to make sure I understand.

Niorlys commented 8 months ago

@danielmorell yes, you are getting the point.