errors
Go error library with error portability over the network (by cockroachdb)
errors
Simple error handling primitives (by pkg)
| errors | errors | |
|---|---|---|
| 6 | 30 | |
| 1,979 | 7,511 | |
| 1.5% | - | |
| 5.1 | 0.2 | |
| 11 days ago | over 2 years ago | |
| Go | Go | |
| Apache License 2.0 | BSD 2-clause "Simplified" License |
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.
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 2023-11-29.
-
Show HN: Error return traces for Go, inspired by Zig
Can you explain why we should this over https://github.com/pkg/errors?
-
Cant wait for less verbose error handling
The pkg/errors package offers some nice add-ons for easier error handling. Too bad it was put into maintenance mode pending whatever changes/improvements are coming in Go 2.
- Error handling and serializing
-
isse for go path in neovim
I can't figure out the issue so here for some help, I am using `neovim/nvim-lspconfig` my `gopls` doesn't recognise external paths such as `github.com/pkg/errors` , it throws error`could not import github.com/pkg/errors (cannot find package "github.com/pkg/errors" in any of /usr/local/go/src/github.com/pkg/errors (from $GOROOT) /Users/ra compiler (BrokenImport)\`
-
What am I supposed to be doing with errors?
Also - there are some error handling utils that allow you to wrap errors before passing: https://github.com/pkg/errors
-
Go error handling is not verbose but the error handling itself.
Should've been something like errors.Newf("failed to foofoo %s", foo) instead and preferably never invent %w but have some controlled way to wrap like errors.Wrapf(err, "failed to foofoo %s", foo) that was in ye olde github.com/pkg/errors.
-
How to wrap the error best?
Prefer using errors.Wrap and errors.Wrapf from https://github.com/pkg/errors . It's frozen because they don't want to add features, waiting for a re-write of error handling in Go2.
- mdobak/go-xerrors: Yet another error handling library.
-
Getting at the type of error after it has been wrapped with errors.Wrap
Im using zerolog and in order to get the stack trace for my error I have to wrap my error in errors.Wrap from "github.com/pkg/errors".
-
When ia a good time to panic?
And for "real programs" you can use https://github.com/pkg/errors (if you want stack traces)
What are some alternatives?
When comparing errors and errors you can also consider the following projects:
golangci-lint - Fast linters Runner for Go
zerolog - Zero Allocation JSON Logger
emperror - The Emperor takes care of all errors personally
autoflags - Populate go command line app flags from config struct
go-multierror - A Go (golang) package for representing a list of errors as a single error.
backward-cpp - A beautiful stack trace pretty printer for C++
logrus - Structured, pluggable logging for Go.
json-logs - A tool to pretty-print JSON logs, like those from zap or logrus.
bitio - Optimized bit-level Reader and Writer for Go.
stacktrace - Stack traces for Go errors
Testify - A toolkit with common assertions and mocks that plays nicely with the standard library