You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Properly handle grouped and chained exceptions. The test case in the
linked issue illustrates that some ExceptionGroups have been handled in
a wrong way.
Updated some tests, because now that those are handled correctly all the
mechanism types except for the root exception are set to "chained" like
described in the RFC:
https://github.com/getsentry/rfcs/blob/main/text/0079-exception-groups.md#interpretation
Because this will change the grouping of exiting Sentry Issues
containing ExceptionGroups, it is safer to release this fix in the next
major and make sure that we describe the change in behavior in the
changelog. (Note: The grouping in the Ariadne issues will not change
because those are not ExceptionGroups and only updating the
`mechanism.type` does not change the grouping)
Fixes#3913
Copy file name to clipboardExpand all lines: MIGRATION_GUIDE.md
+1Lines changed: 1 addition & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -22,6 +22,7 @@ Looking to upgrade from Sentry SDK 2.x to 3.x? Here's a comprehensive list of wh
22
22
- clickhouse-driver integration: The query is now available under the `db.query.text` span attribute (only if `send_default_pii` is `True`).
23
23
-`sentry_sdk.init` now returns `None` instead of a context manager.
24
24
- The `sampling_context` argument of `traces_sampler` and `profiles_sampler` now additionally contains all span attributes known at span start.
25
+
- We updated how we handle `ExceptionGroup`s. You will now get more data if ExceptionGroups are appearing in chained exceptions. It could happen that after updating the SDK the grouping of issues change because of this. So eventually you will see the same exception in two Sentry issues (one from before the update, one from after the update)
25
26
- The integration-specific content of the `sampling_context` argument of `traces_sampler` and `profiles_sampler` now looks different.
26
27
- The Celery integration doesn't add the `celery_job` dictionary anymore. Instead, the individual keys are now available as:
0 commit comments