| errcode | xtrace | |
|---|---|---|
| 1 | 1 | |
| 14 | 4 | |
| - | - | |
| 2.8 | 0.0 | |
| 6 months 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.
errcode
Posts with mentions or reviews of errcode.
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
I believe the solution to this is to classify errors properly. Any "internal error" as in HTTP 500 Internal Error should be generating a stack trace. Most other expected errors (like your case) should not. I codified this practice in a library I created for Go called errcode [1] which is designed to attach error codes and other meta information where errors are generated.
[1] https://github.com/pingcap/errcode
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 errcode and xtrace you can also consider the following projects:
json-logs - A tool to pretty-print JSON logs, like those from zap or logrus.
backward-cpp - A beautiful stack trace pretty printer for C++
logutil - Utils for use with zerolog
zerolog - Zero Allocation JSON Logger
golangci-lint - Fast linters Runner for Go
errors - Simple error handling primitives
errors - Go error library with error portability over the network
go - The Go programming language