errors
DISCONTINUED
errors
Our great sponsors
errors | errors | |
---|---|---|
30 | 6 | |
7,511 | 1,944 | |
- | 2.3% | |
0.2 | 6.5 | |
over 2 years ago | about 1 month ago | |
Go | Go | |
BSD 2-clause "Simplified" License | Apache License 2.0 |
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
-
Show HN: Error return traces for Go, inspired by Zig
Can you explain why we should this over https://github.com/pkg/errors?
- Error handling and serializing
-
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
-
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.
-
When ia a good time to panic?
And for "real programs" you can use https://github.com/pkg/errors (if you want stack traces)
-
My next client wants to redevelop a java Webapp with go
pkg/errors or stdlib errors - Error handling, but I wrote my own package for that tailored to my projects' needs. (FYI primalskill/errors but please don't use it as it's not production-ready yet and it will change a lot)
-
What are some good open source project to read when learning Go?
https://github.com/pkg/errors - errors with stack traces
-
Anyone using github.com/pkg/errors for stack traces?
The pkg.go.dev page lists 14k+ projects importing it, but the Github repository has been archived which would seem to discourage use. I'm also not a huge fan of the naming conflict with the stdlib errors package. The README notes it went into maintenance mode but it appears this, too, has passed.
-
go-faster/errors: clear go error wrapping with caller (xerrors fork with Wrap)
The pkg/errors and xerrrors are not maintainted
errors
-
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.
What are some alternatives?
zerolog - Zero Allocation JSON Logger
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.
logrus - Structured, pluggable logging for Go.
bitio - Optimized bit-level Reader and Writer for Go.
Testify - A toolkit with common assertions and mocks that plays nicely with the standard library
errorx - A comprehensive error handling library for Go
uuid - Generate, encode, and decode UUIDs v1 with fast or cryptographic-quality random node identifier.
go-chat-bot - IRC, Slack, Telegram and RocketChat bot written in go
vfs for golang - Virtual filesystem library written in golang
chi - lightweight, idiomatic and composable router for building Go HTTP services
Miniflux - Minimalist and opinionated feed reader