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

Stack traces missing from inner exceptions of aggregate exceptions #1917

Closed
mattjohnsonpint opened this issue Sep 13, 2022 · 1 comment · Fixed by #1922
Closed

Stack traces missing from inner exceptions of aggregate exceptions #1917

mattjohnsonpint opened this issue Sep 13, 2022 · 1 comment · Fixed by #1922
Assignees
Labels
Bug Something isn't working

Comments

@mattjohnsonpint
Copy link
Contributor

mattjohnsonpint commented Sep 13, 2022

SDK Version

3.21.0

Steps to Reproduce

using Sentry;

using (SentrySdk.Init(o =>
       {
           o.Dsn = "https://eb18e953812b41c3aeb042e666fd3b5c@o447951.ingest.sentry.io/5428537";
           o.Debug = true;
       }))
{
    throw new AggregateException(new MyException());
}

public class MyException : Exception
{
}

Expected Result

The AggregateException should be filtered out, and Sentry should capture the unhandled MyException, retaining the stack trace.

Actual Result

The AggregateException is filtered out, but the stack trace is gone also.

We need to copy over the stack trace when filtering out aggregate exceptions.

@mattjohnsonpint mattjohnsonpint added Bug Something isn't working Platform: .NET labels Sep 13, 2022
@mattjohnsonpint
Copy link
Contributor Author

Also missing mechanism and extra data. These are only left on the aggregate, so they need to be copied over to the last exception sent to Sentry. (Sentry expects exceptions from oldest to newest.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Something isn't working
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

1 participant