Re: [go-nuts] go env doesn't seem to work well with GOTELEMETRY

On Tue, Aug 20, 2024 at 7:00 PM Will Faught wrote: > > Thanks, but it looks like that issue is only about enabling `go env -w > GOTELEMETRY=off`. > > Isn't it incorrect for `go env GOTELEMETRY` to work, yet `go env -u > GOTELEMETRY` prints `unknown go command variable GOTELEMETRY`? Shouldn't it

Re: [go-nuts] go env doesn't seem to work well with GOTELEMETRY

Thanks, but it looks like that issue is only about enabling `go env -w GOTELEMETRY=off`. Isn't it incorrect for `go env GOTELEMETRY` to work, yet `go env -u GOTELEMETRY` prints `unknown go command variable GOTELEMETRY`? Shouldn't it insead print something like `go command variable GOTELEMETRY cann

Re: [go-nuts] go env doesn't seem to work well with GOTELEMETRY

On Tue, Aug 20, 2024 at 5:08 PM will@gmail.com wrote: > > Despite showing up an an env var, it's not treated consistently as one: > > ❯ go telemetry off > # nothing printed > # as expected > > ❯ go env | grep GOTELEMETRY= > GOTELEMETRY='off' > # as expected > > ❯ go env GOTELEMETRY > off > # a

Re: [go-nuts] segmention fault while upgrading from 1.20.6 to 1.22.3

Have you tried 1.21.x? Not sure if this is something that might happen only in 1.22.3? On Tuesday, August 20, 2024 at 11:07:11 AM UTC-6 Ian Lance Taylor wrote: > On Tue, Aug 20, 2024 at 5:34 AM M.Tarkeshwar Rao > wrote: > > > > As part of regular LCM activity we are doing GoLang LCM. Issue is:

[go-nuts] go env doesn't seem to work well with GOTELEMETRY

Despite showing up an an env var, it's not treated consistently as one: ❯ go telemetry off # nothing printed # as expected ❯ go env | grep GOTELEMETRY= GOTELEMETRY='off' # as expected ❯ go env GOTELEMETRY off # as expected ❯ go env -changed # nothing printed # as expected ❯ go env -u GOTELEMET

Re: [go-nuts] segmention fault while upgrading from 1.20.6 to 1.22.3

On Tue, Aug 20, 2024 at 5:34 AM M.Tarkeshwar Rao wrote: > > As part of regular LCM activity we are doing GoLang LCM. Issue is: > > This is to bring to your immediate attention that while doing golang LCM , > we changed it to 1.22.3 but CI job failed on the same . > Upon debugging application it w

[go-nuts] segmention fault while upgrading from 1.20.6 to 1.22.3

Hi all, As part of regular LCM activity we are doing GoLang LCM. Issue is: This is to bring to your immediate attention that while doing golang LCM , we changed it to 1.22.3 but CI job failed on the same . Upon debugging application it was deduced that there may be memory issue. But even after

[go-nuts] Re: how to attach the pkg revision during go install

As a reference, you could look at how prometheus does it: % go install github.com/prometheus/prometheus/cmd/prometheus % ~/go/bin/prometheus --version prometheus, version (branch: , revision: b914a9b580abd7bb7e879602c17fea0e06fd0266) ... I know it uses a build utility (promu) to embed the info