errors
Go error library with error portability over the network (by cockroachdb)
xtrace
A simple library to extract traces from golang's xerrors (by ollien)
| errors | xtrace | |
|---|---|---|
| 6 | 1 | |
| 1,979 | 4 | |
| 1.5% | - | |
| 5.1 | 0.0 | |
| 12 days ago | about 4 years ago | |
| Go | Go | |
| Apache License 2.0 | Apache License 2.0 |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
errors
Posts with mentions or reviews of errors.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-03-29.
-
Who returns specific error interfaces to model domain errors?
I usually use https://github.com/cockroachdb/errors for reasons that you can read in their documentation. It is well thought out and is no more complicated than it needs to be. It is a drop in replacement for the standard errors package and they have built this from experience, which is usually a good thing. It is usually best to stick to interfaces. With concrete errors, you will be doomed to deal with them forever.
-
Go's Error Handling Is a Form of Storytelling
https://github.com/cockroachdb/errors has worked great for me! Agreed this should be part of the core language though.
-
Anyone using github.com/pkg/errors for stack traces?
https://github.com/cockroachdb/errors is the most featureful in this space, but is heavy if you don't need network portability, redaction, and all the other bells and whistles.
-
go-faster/errors: clear go error wrapping with caller (xerrors fork with Wrap)
The cockroachdb/errors is too big
- Error stack traces in Go with x/xerror
-
Comparison golang stacktrace error library output
Golang is great. I mostly love it. However, collecting an error with relevant context and a nicely formatted stacktrace is kind of a mess of competing approaches. This this feature comparison is a good overview of the landscape.
xtrace
Posts with mentions or reviews of xtrace.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2021-08-23.
-
Error stack traces in Go with x/xerror
Like the article mentions, they didn't bring over stack traces (namely the `Formatter` interface) from xerrors. I wrote a library[1] around it that would generate true stack traces. I don't use it as much as I used to, because I don't want to depend on a package like xerrors I don't trust to remain maintained, but it was a fun exercise at the time, and very useful while I used it. I wish that we wouldn't have to depend on a tool like Sentry for bringing this about, like the author suggests.
https://github.com/ollien/xtrace
What are some alternatives?
When comparing errors and xtrace you can also consider the following projects:
golangci-lint - Fast linters Runner for Go
errcode
emperror - The Emperor takes care of all errors personally
backward-cpp - A beautiful stack trace pretty printer for C++
zerolog - Zero Allocation JSON Logger
json-logs - A tool to pretty-print JSON logs, like those from zap or logrus.
errors - Simple error handling primitives
logutil - Utils for use with zerolog