We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
CoreCrashedError
Before the 7.12.1 release we saw all the core errors that led to an actual core crash as CoreCrashedError.
the 7.12.1
Thanks to changes in the #7021 we are now able to see the real exception inside the Stacktrace field (see #7065 as an example).
Stacktrace
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.
The text was updated successfully, but these errors were encountered:
This is an example of the desired Sentry Event: https://sentry.tribler.org/organizations/tribler/issues/1747
Sorry, something went wrong.
CoreError
drew2a
Successfully merging a pull request may close this issue.
Before
the 7.12.1
release we saw all the core errors that led to an actual core crash asCoreCrashedError
.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.The text was updated successfully, but these errors were encountered: