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

Extract a real core error from CoreCrashedError for the Sentry Reporter #7066

Closed
drew2a opened this issue Sep 26, 2022 · 1 comment · Fixed by #7072
Closed

Extract a real core error from CoreCrashedError for the Sentry Reporter #7066

drew2a opened this issue Sep 26, 2022 · 1 comment · Fixed by #7072
Assignees
Milestone

Comments

@drew2a
Copy link
Contributor

drew2a commented Sep 26, 2022

Before the 7.12.1 release we saw all the core errors that led to an actual core crash as CoreCrashedError.

Thanks to changes in the #7021 we are now able to see the real exception inside the Stacktrace field (see #7065 as an example).

But sentry still use CoreCrashedError as the type for the exception (see https://sentry.tribler.org/organizations/tribler/issues/1619).

It would be nice to extract the real exception from the Stacktrace field and use it as an exception that Tribler sends to the Sentry.

@drew2a drew2a self-assigned this Sep 26, 2022
@drew2a drew2a added this to the 7.13.0 milestone Sep 26, 2022
@drew2a
Copy link
Contributor Author

drew2a commented Sep 29, 2022

This is an example of the desired Sentry Event:
https://sentry.tribler.org/organizations/tribler/issues/1747

image

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

Successfully merging a pull request may close this issue.

1 participant