Skip to content
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

Rollbar reporting ExceptionGroup instead of the raised exception #441

Open
Niorlys opened this issue Oct 19, 2023 · 2 comments
Open

Rollbar reporting ExceptionGroup instead of the raised exception #441

Niorlys opened this issue Oct 19, 2023 · 2 comments
Assignees

Comments

@Niorlys
Copy link

Niorlys commented Oct 19, 2023

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 danielmorell self-assigned this Oct 20, 2023
@danielmorell
Copy link
Collaborator

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
Copy link
Author

Niorlys commented Oct 20, 2023

@danielmorell yes, you are getting the point.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants