We've been doing this via an in-house errors package for a while. It does other things, like log request ID with the error for tracing and whatnot, and uses a b

We've been doing this via an in-house errors package for a while. It does other things, like log request ID with the error for tracing and whatnot, and uses a bit of code adopted from panicparse [0] to print pretty, easy-on-the-eyes, quickly-parsable stack traces. Honestly I don't know why stack traces aren't formatted for quick parsing. Many thanks to maruel [1] for the inspiration. [0] https://github.com/maruel/panicparse https://github.com/maruel/panicparse [1] https://github.com/maruel https://github.com/maruel