Skip to content
This repository has been archived by the owner on Aug 30, 2023. It is now read-only.

Use cause in place of err in GetOrNewStacktrace #155

Merged
merged 1 commit into from
Nov 11, 2017

Conversation

martinxsliu
Copy link
Contributor

Many thanks to @jsm and @mattrobenolt for getting the pkg/errors integration piece merged in #152!

This PR fixes an issue where the cause wasn't actually being passed into GetOrNewStacktrace, meaning the generated stacktrace was of the last wrapped error rather than the originating one.

This PR also adds the integration into the CaptureErrorAndWait method in addition to the current CaptureError.

@mattrobenolt mattrobenolt merged commit 69575a0 into getsentry:master Nov 11, 2017
@mattrobenolt
Copy link
Contributor

Thanks! 🍕

@jsm
Copy link
Contributor

jsm commented Jan 23, 2018

@martinxsliu This causes any causes not created with the errors package to lose the stacktrace.

Instead of passing the cause into GetOrNewStacktrace, we should instead recursively find the deepest cause that still has a stacktrace in GetOrNewStacktrace

@martinxsliu
Copy link
Contributor Author

@jsm I just made this PR a minute ago #167 :)

@jsm
Copy link
Contributor

jsm commented Jan 23, 2018

@martinxsliu We are in sync it would seem haha

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants