stacktrace
stacktrace copied to clipboard
palantir
Stack traces for Go errors
I realize it is probably too late to change this behavior, but I still think it is worthwhile flagging a bug I found recently. if you have already declared err...
This change adds support for `errors.Unwrap` functionality originally introduced in Golang 1.13. While the library code does not need to take multiple Golang versions into account, the testing code needs...
Go 1.13 introduced error wrapping. It would be beneficial if `palantir/stacktrace` supported it so that errors could still be compared after propagation.
RootMessage returns message associated with root error in stack. This allows us to get root error message and use it to, i.e, return to user without any additional structs.
The new [slog](https://pkg.go.dev/golang.org/x/exp/slog) library provides a `slog.LogValuer` interface for formatting attributes. Documentation here: https://pkg.go.dev/golang.org/x/exp/slog#hdr-Customizing_a_type_s_logging_behavior I think palantir/stacktrace should implement it. ```go type customError struct { ... } func (e customError)...
There is a common pattern in domain logic, where the creation of errors has been standardised with helper functions. For example in a http handler one might want to easily...
###### _excavator_ is a bot for automating changes across repositories. Changes produced by the excavator/bulldozer-oss check. To enable or disable this check, please contact the maintainers of Excavator.
###### _excavator_ is a bot for automating changes across repositories. Changes produced by the excavator/excavator-yml-oss check. To enable or disable this check, please contact the maintainers of Excavator.