-
Notifications
You must be signed in to change notification settings - Fork 444
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
Proposal for Improving Error Reporting Mechanism in Sentry #8051
Labels
Comments
drew2a
changed the title
Format Sentry issue
Proposal for Improving Error Reporting Mechanism in Sentry
Jun 3, 2024
As QT based UI is removed from the main codebase, this issue has become obsolete. Therefore, I'm unassigning myself. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We have the very first Sentry issue reported by @xoriole's new mechanism for error reporting.
The great news is that it is working, and the mechanism can be improved further.
Currently, the formatting of the Event is as follows:
This links together two issues:
and
The real issue with the stack trace is buried somewhere inside the event:
My proposition is that the real issue with its stack trace should be easily accessible in the report and should not be substituted by CoreCrashedError.
Also, it seems that the excessive core output is captured for the issue description:
Where the necessary part is
and the excessive is
Related:
The text was updated successfully, but these errors were encountered: