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
{{ message }}
This repository was archived by the owner on Aug 30, 2023. It is now read-only.
cause gets used for the Stacktrace generation. However, Cause is called on the result of errors.WithStack, which simply removes that layer, so we don't have a trace anymore.
Is there a reason why Cause is used here? Maybe instead of always taking the Cause, check if the current err has a Stacktrace and cause has not, and use the stack of err?
Right now, if your error is the following:
it will not use that stacktrace. The reason is in
client.go:raven-go/client.go
Lines 710 to 712 in 3033899
causegets used for the Stacktrace generation. However,Causeis called on the result oferrors.WithStack, which simply removes that layer, so we don't have a trace anymore.Is there a reason why
Causeis used here? Maybe instead of always taking theCause, check if the currenterrhas a Stacktrace andcausehas not, and use the stack oferr?