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 has been 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?
The text was updated successfully, but these errors were encountered:
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
cause
gets used for the Stacktrace generation. However,Cause
is called on the result oferrors.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 theCause
, check if the currenterr
has a Stacktrace andcause
has not, and use the stack oferr
?The text was updated successfully, but these errors were encountered: