Re: [go-nuts] Best Practices for Error Handling in Go APIs

> On Feb 4, 2025, at 4:59 PM, Darren Grant wrote: > > What's the current best practice for getting a stack trace from an error > passed up from further down in the stack? > > E.g. a web server middleware uses recover to catch panics. In the recover, we > want the stack trace of the code that c

[go-nuts] Re: Best Practices for Error Handling in Go APIs

What's the current best practice for getting a stack trace from an error passed up from further down in the stack? E.g. a web server middleware uses recover to catch panics. In the recover, we want the stack trace of the code that created the first error in the stack. On Monday, 3 February 202

[go-nuts] Generic memory repository

Hi there! ¿How you doing? I'm trying to implement a simple in-memory storage, that holds entities under a map. The entities shall be identificables, as they have an Id. And I want that id to be set by the underlying persistent subsystem on creation time. So I wrote this type Identificable inte

[go-nuts] [security] Go 1.23.6 and Go 1.22.12 are released

Hello gophers, We have just released Go versions 1.23.6 and 1.22.12, minor point releases. These minor releases include 1 security fixes following the security policy : - crypto/elliptic: timing sidechannel for P-256 on ppc64le Due to the usage of a varia