[go-nuts] [ANN] Easy-to-use Histogram has been added to github.com/VictoriaMetrics/metrics package

Nice! Thanks for this simple and easy to use metric client library! -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To

[go-nuts] macOS binaries and installer identifiers are changing

Hi folks Per golang.org/issue/35854, on macOS, we are updating our Go package identifier namespace from com.googlecode.* to org.golang.*. If your infrastructure relies on our installer having a specific identifier, you should use the new value starting with 1.13.5 and 1.12.14, which have yet to be

Re: [go-nuts] Change slice type

On Tue, Nov 26, 2019 at 5:47 AM wrote: > > When i have a buffer > x:=make([]byte, 0, 8) > > Is it possible to use same memory range as []int of size: > FLOOR(8*size_of(byte)/size_of(int)). Basically i want to make slab > allocator better It is possible to do this using the unsafe

[go-nuts] [ANN] Easy-to-use Histogram has been added to github.com/VictoriaMetrics/metrics package

If you don't instrument your Go apps with custom metrics exported via Prometheus format, then stop reading. Prometheus histograms have multiple long-standing issues, which limit histograms usability: - How to choose the ultimate set of histogram buckets that cover all the value ranges with

[go-nuts] Change slice type

Hi Guys, quick question... When i have a buffer x:=make([]byte, 0, 8) Is it possible to use same memory range as []int of size: FLOOR(8*size_of(byte)/size_of(int)). Basically i want to make slab allocator better Thanks -- You received this message because you are subscribed to the

[go-nuts] Re: Regexp for email

at this regexp its giving warning bad syntax tag i finding how this issues will resolve di you know On Monday, July 5, 2010 at 4:01:52 PM UTC+5, Archos wrote: > > Here I use a *simple* regexp. to validate email addresses, but it > doesn't validates like I expect. > > It looks me that the

Re: [go-nuts] runtime: panic in net/http.(*Server).Serve

Just because you print all of the parameters and they’re ok doesn’t mean there isn’t any corruption. Sorry I can’t be of more help. > On Nov 26, 2019, at 3:22 AM, 黃翔蔚 wrote: > >  > Hi Robert, > Thanks for the explanation. > There is only one function call from GO to CPP in the program. > I

Re: [go-nuts] [ANN] Golang Oriented to Aspects (goa) v0.0.1 is released!!!

Done! thanks for comment On Tuesday, November 26, 2019 at 11:57:08 AM UTC+1, Jan Mercl wrote: > > On Mon, Nov 25, 2019 at 10:47 PM Iván Corrales Solera > > wrote: > > > Source ode https://github.com/wesovilabs/goa > > Full documentation http://wesovilabs.github.io/goa > > Would you mind

Re: [go-nuts] [ANN] Golang Oriented to Aspects (goa) v0.0.1 is released!!!

On Mon, Nov 25, 2019 at 10:47 PM Iván Corrales Solera wrote: > Source ode https://github.com/wesovilabs/goa > Full documentation http://wesovilabs.github.io/goa Would you mind changing the name of the language to the proper form everywhere in the above quoted links? Some people may chose to

[go-nuts] Re: [ANN] Golang Oriented to Aspects (goa) v0.0.1 is released!!!

I would like to share this article in which I describe a real use case https://medium.com/@ivan.corrales.solera/aop-to-the-rescue-detecting-performance-issues-in-go-applications-4d00325fbd13 I hope you enjoy it! On Monday, November 25, 2019 at 10:46:57 PM UTC+1, Iván Corrales Solera wrote: > >

Re: [go-nuts] runtime: panic in net/http.(*Server).Serve

Hi Robert, Thanks for the explanation. There is only one function call from GO to CPP in the program. I printf all parameters in the CPP function. There is no memory corruption inside. If you have any other troubleshooting suggestions, I would appreciate it. Walter Robert Engels於 2019年11月26日星期二