Eris – A better way to handle, trace, and log errors in Go • Hacker News Board

Eris – A better way to handle, trace, and log errors in Go

#1

Post by sum2000 » Wed, Dec 25, 2019, 7:00 PM UTC

Eris – A better way to handle, trace, and log errors in Go
github.com

Re: Eris – A better way to handle, trace, and log errors in Go

#2

Post by lowmagnet » Wed, Dec 25, 2019, 8:37 PM UTC

IDK about the error json, looks too much like a PHP dump when a descriptive error wrapper will do.

Re: Eris – A better way to handle, trace, and log errors in Go

#3

Post by holaatme » Wed, Dec 25, 2019, 9:01 PM UTC

lowmagnet wrote: post #2

IDK about the error json, looks too much like a PHP dump when a descriptive error wrapper will do.

If you are reading the JSON yourself, you’re doing it wrong. JSON logs can be parsed and stored for analysis and generally deal with multi line issues much better than any non json.

Re: Eris – A better way to handle, trace, and log errors in Go

#4

Post by morningvera » Wed, Dec 25, 2019, 9:07 PM UTC

My friend and I have been working on eris for a while and we’re very excited to get feedback from fellow gophers. eris provides a better way to handle, trace, and log errors in Go. More info here github.com/rotisserie/eris and godoc.org/github.com/rotisserie/eris

You can reach out to us on slack (gorotisserie.slack.com/archives/CS13EC3T6) for additional comments and feedback. Thanks!

Re: Eris – A better way to handle, trace, and log errors in Go

#5

Post by nicpottier » Wed, Dec 25, 2019, 9:19 PM UTC

morningvera wrote: post #4

My friend and I have been working on eris for a while and we’re very excited to get feedback from fellow gophers. eris provides a better way to handle, trace, and log errors in Go. More info here github.com/rotisserie/eris and godoc.org/github.com/rotisserie/eris You can reach out to us on slack (gorotisserie.slack.com/archives/CS13EC3T6) for additional comments and feedback. Thanks!

Looks nice! Any plans to add support for uploading stacks to Sentry? That's a must have for us and why we are using pkg/errors.

Re: Eris – A better way to handle, trace, and log errors in Go

#6

Post by morningvera » Wed, Dec 25, 2019, 9:21 PM UTC

nicpottier wrote: post #5

morningvera wrote: post #4

My friend and I have been working on eris for a while and we’re very excited to get feedback from fellow gophers. eris provides a better way to handle, trace, and log errors in Go. More info here github.com/rotisserie/eris and godoc.org/github.com/rotisserie/eris You can reach out to us on slack (gorotisserie.slack.com/archives/CS13EC3T6) for additional comments and feedback. Thanks!

Looks nice! Any plans to add support for uploading stacks to Sentry? That's a must have for us and why we are using pkg/errors.

Thanks! We'd love to add support if you need it. I'll make a note of it but feel free to add an issue for it if you have time!

Re: Eris – A better way to handle, trace, and log errors in Go

#7

Post by erik_seaberg » Wed, Dec 25, 2019, 9:29 PM UTC

Stack traces and structured output are handy, but I was hoping for a way to factor out the handler boilerplate that makes app code unreadable (like the "check" or "try" proposal for future versions).

Re: Eris – A better way to handle, trace, and log errors in Go

#8

Post by caylus » Wed, Dec 25, 2019, 9:56 PM UTC

This is really cool! My company has a similar internal library but it doesn't format wrapped errors as well as Eris.

One other issue I've struggled with is in propagating errors across goroutines. If an error is created in the child routine, `runtime.Callers` doesn't include any stack frames from the parent. Assuming the parent wraps the error, it sounds like Eris would give you at least one line of the parent stack trace. Does it handle this specifically by including all of them?

Re: Eris – A better way to handle, trace, and log errors in Go

#9

Post by awinter-py » Wed, Dec 25, 2019, 10:20 PM UTC

Have spent a while in the py/js world but have switched to rust/go for part of this year -- biggest change is boilerplate relating to error handling.

Automatic stack capture for exceptions is something my language could conceivably do on my behalf.

Writing even 3 lines of code per function to propogate up the error is a huge pain, especially because it pollutes the return type -- MustWhatever() in go is much easier to use than Whatever() returning (type, err)

Re: Eris – A better way to handle, trace, and log errors in Go

#10

Post by sagichmal » Wed, Dec 25, 2019, 11:11 PM UTC

awinter-py wrote: post #9

Have spent a while in the py/js world but have switched to rust/go for part of this year -- biggest change is boilerplate relating to error handling. Automatic stack capture for exceptions is something my language could conceivably do on my behalf. Writing even 3 lines of code per function to propogate up the error is a huge pain, especially because it pollutes the return type -- MustWhatever() in go is much easier t…

You're fighting the language. Unless you're writing prototypes where crashing doesn't matter, you should be writing error handling code first, and your business logic second -- so-called "sad path first" programming, c.f. "happy-path first" programming that you usually do in languages with exceptions like Python.