[go-nuts] Re: rsc.io/script: How to contribute?

I have had a good experience using https://github.com/commander-cli/commander for testing CLI commands. It uses a yaml file for test config. I generally avoid yaml but the commander config format is easy to work with. Never used script, the state saving between commands feature might be

Re: [go-nuts] GO111MODULE=off go get deprecated?

On Wed, Mar 6, 2024 at 11:53 AM Jeffery Carr wrote: > On Sunday, March 3, 2024 at 5:46:13 PM UTC-6 Christian Stewart wrote: > Second, you can use "go work" to create a workspace with multiple go > modules in it, so that you can develop with them without having to > constantly update the go.mod

[go-nuts] Re: rsc.io/script: How to contribute?

*rsc.io/script On Wednesday, March 6, 2024 at 10:46:23 PM UTC+1 twp...@gmail.com wrote: > Internally, Go has a very nice package for integration testing > . > > Roger Peppe has been doing a

[go-nuts] rsc.io/script: How to contribute?

Internally, Go has a very nice package for integration testing . Roger Peppe has been doing a fantastic service by making it public and maintaining it as a community project at

Re: [go-nuts] GO111MODULE=off go get deprecated?

On Sunday, March 3, 2024 at 5:46:13 PM UTC-6 Christian Stewart wrote: Firstly, you can reference the other repos and use the latest "master" version by writing "master" where the v verson is in the file, then use "go mod tidy" Second, you can use "go work" to create a workspace with

Re: [go-nuts] GO111MODULE=off go get deprecated?

On Tuesday, March 5, 2024 at 9:29:58 AM UTC-6 Bryan C. Mills wrote: Part of the intent with modules is that you do not need to do a full `git clone` of each dependency — you should really only need to do that if you need to author upstream changes yourself, Yes, I'm authoring upstream

[go-nuts] Re: How to add labels to Go runtime prometheus metrics?

Situation here may be a bit specific. Running 2 cloud machines behind reverse proxy. I realise this is per chance if the proxy will hit any of the two, but that would be good enough id I could distinguish their metrics. On Wednesday, March 6, 2024 at 1:38:12 PM UTC+1 Brian Candler wrote: > The

Re: [go-nuts] Query Regarding ASAN C Call from Go Code

I encountered an issue when trying to use pragma *//go:cgo_export_static *in my Go code similar to the *ASAN* code. https://github.com/golang/go/blob/f0d1195e13e06acdf8999188decc63306f9903f5/src/runtime/asan.go#L65 It seems there is a check in the compile utility preventing this.

[go-nuts] Re: Why Go opt for using * in signature of function that returns a pointer instead of using &?

Matheus, Rewire your brain. The return value or values may be explicitly listed in the "return" statement. Each expression must be single-valued and assignable to the corresponding element of the function's result type. The Go Programming Language Specification

Re: [go-nuts] Why Go opt for using * in signature of function that returns a pointer instead of using &?

Thank for your answers, makes a lot of sense. Em quarta-feira, 6 de março de 2024 às 02:24:50 UTC-3, Kurtis Rader escreveu: > Anyone familiar with C/C++ will be familiar with the current convention of > using an asterisk to indicate a pointer to the value. Yes, there is a > reasonable

[go-nuts] Re: How to add labels to Go runtime prometheus metrics?

The server name will be added by Prometheus itself as an "instance" label for each target being scraped (or you can manually set the instance label for each target), so in general what you're asking is not necessary. None of the standard Prometheus exporters include a label for the hostname

[go-nuts] How to add labels to Go runtime prometheus metrics?

The Go runtime exposes various metrics. To collect metrics from multiple servers I'd like to add labels for server name. Is it possible to extend the build-in metrics for this purpose? Thanks, Andi -- You received this message because you are subscribed to the Google Groups "golang-nuts"