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
Zap currently only filters our runtime stack frames and the last takeStacktrace function, but not the other zap frames. This leads to stack traces like:
Currently, zap only filters out runtime stackframes, which leaves a lot
of noise from zap (Error, log, check, etc). This modifies the stacktrace
to filter out all zap frames at the beginning of the stack. It will not
filter out zap stacks in between non-zap frames.
Fixes#488.
Currently, zap only filters out runtime stackframes, which leaves a lot
of noise from zap (Error, log, check, etc). This modifies the stacktrace
to filter out all zap frames at the beginning of the stack. It will not
filter out zap stacks in between non-zap frames.
Fixes#488.
Zap currently only filters our runtime stack frames and the last
takeStacktrace
function, but not the other zap frames. This leads to stack traces like:From #308 (comment)
Or if the package is installed through a vendor directory:
The
Errorf
etc don't really provide much value, so we should remove zap stack frames, even when they're in vendor.The text was updated successfully, but these errors were encountered: