uhoh
errors
uhoh | errors | |
---|---|---|
1 | 30 | |
4 | 7,511 | |
- | - | |
0.0 | 0.2 | |
over 2 years ago | over 2 years ago | |
Go | Go | |
- | BSD 2-clause "Simplified" License |
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.
uhoh
-
Uhoh
Hey everyone. I have had the need to log stack tracing for my errors. I wanted to know if anyone else feels the same way. I built a simple error package that will set stack trace values and has methods for outputting to map string and json. Let me know if you think this is valuable or if there is anything else you would add or change to it. https://github.com/brianvoe/uhoh
errors
-
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?
panicparse - Crash your app in style (Golang)
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
uuid - Generate, encode, and decode UUIDs v1 with fast or cryptographic-quality random node identifier.
errorx - A comprehensive error handling library for Go
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