Re: [go-nuts] x/pkgsite docs wrongly assume $PATH includes $GOPATH/bin

I've created an issue for this on Golang's Github , let's see where that goes. I went for the "let's add to the docs first" approach for now. Thanks for the convo! On Thursday 29 February 2024 at 09:25:00 UTC+1 Axel Wagner wrote: > On Thu, Feb 29,

[go-nuts] logout/end session

Using token and the log in request struct i.e (userId, sessionId, timestamp) i generated a login/auth for log in process by creating and merging the request payload to generate the signature thus comparing for varification so the user is active in the system how will i end the session using

[go-nuts] Re: [security] Go 1.22.1 and Go 1.21.8 pre-announcement

Hello gophers, We accidentally repeated one of the CVEs in the pre-announcement. The correct list of CVEs being fixed are: - CVE-2024-24783 - CVE-2023-45290 - CVE-2023-45289 Thanks, Carlos for the Go team On Thursday, February 29, 2024 at 6:29:01 PM UTC-5 annou...@golang.org wrote:

[go-nuts] [security] Go 1.22.1 and Go 1.21.8 pre-announcement

Hello gophers, We plan to issue Go 1.22.1 and Go 1.21.8 during US business hours on Tuesday, March 5. These minor releases include PRIVATE security fixes to the standard library, covering the following CVEs: - CVE-2023-45289 - CVE-2023-45290 - CVE-2023-45289 Following our

Re: [go-nuts] Could we trade all the `ctx context.Context` arguments for one pointer in `g`?

Thanks for your examples!  I'll cover them in reverse order, to build up the syntax. On 2/29/24 6:18 AM, 'TheDiveO' via golang-nuts wrote: The second example is unit test code, so TEST:

Re: [go-nuts] Equality of interface of an empty struct - why?

On Thursday, February 29, 2024 at 7:04:14 PM UTC+8 Axel Wagner wrote: Yes. It means "violating a rule, without setting a precedent for future violations". One of the main objections to the loop variable change has been the breaking of compatibility and the fear of setting a precedent for

Re: [go-nuts] Equality of interface of an empty struct - why?

On Thursday, February 29, 2024 at 3:14:40 PM UTC+8 Axel Wagner wrote: The loop var change *does* break compatibility. And it did so knowingly and - as clearly explained - was an exception. Stop arguing in bad faith. An exception. :D On Thu, Feb 29, 2024 at 7:03 AM tapi...@gmail.com

[go-nuts] gomobile - no stack traces on Android

With gomobile, I’m not able to see stack traces for errors in the native library. For example: ``` 02-29 00:50:16.021 10940 0 E Go : panic: runtime error: invalid memory address or nil pointer dereference 02-29 00:50:16.021 10940 0 E Go : [signal SIGSEGV: segmentation

Re: [go-nuts] x/pkgsite docs wrongly assume $PATH includes $GOPATH/bin

On Thu, Feb 29, 2024 at 9:12 AM kredop...@gmail.com wrote: > Apologies - sent the response only to you, so I'll write it again here. > > > Doesn't the `go install` command explicitly instruct you to add > $GOBIN/$GOPATH/bin to your $PATH? > > I did check both golang installation docs and the

Re: [go-nuts] x/pkgsite docs wrongly assume $PATH includes $GOPATH/bin

Apologies - sent the response only to you, so I'll write it again here. > Doesn't the `go install` command explicitly instruct you to add $GOBIN/$GOPATH/bin to your $PATH? I did check both golang installation docs and the output of `go help install` - it's very possible I'm missing something,