Wes McNamee
Wes McNamee
actually what would be great is the ability to choose your stacktrace method, allow the caller to decide if they want to just print the error with `%+v` as the...
I'm also running into this issue.
Really, what I would like is for the cause trace provided by `pkg/errors` to be pretty-printed so that I can read it. Right now, the formatting is that it provides...
@MichaHoffmann do you have an example of how this would look and be printed? Is this how Zap currently prints the stacktrace in dev mode?
@MichaHoffmann I see what you are saying, but I think the original issue that the author is asking for is that this is an extra field that gets forced upon...
I've forked this issue, as I believe the concerns are related but different. I would imagine that implementation of #732 would print the error cause trace like it would the...
@MichaHoffmann is it possible to write a "composite" stacktracer? One that will print the real stack trace on the error cause trace?
@yqylovy what makes you say it's not clean code?
I don't see a reason why you can't do a full match on the registry as compared to what's in the FROM statement. This should be backwards compatible. If someone...
Similar to #401