Re: [go-nuts] tagging releases of x/crypto

On Tue, Sep 19, 2017 at 5:42 PM, Ian Lance Taylor wrote: > On Tue, Sep 19, 2017 at 9:36 AM, 'Peter Moody' via golang-nuts > wrote: >> >> We're big consumers of the x/crypto packages, but the lack of semantic >> versioning tags means that our dependency management tools can easily >> pull in incom

Re: [go-nuts] WaitGroup Count

This is something super cool :D why couldn't I think of this :) On Friday, August 28, 2015 at 1:34:05 PM UTC+4, Jan Mercl wrote: > > On Fri, Aug 28, 2015, 11:04 Enric Lafont gmail.com > > wrote: > > > If the need for Count() is actually just a need to limit a number of > things, for example goro

Re: [go-nuts] Does golang support SystemTap well?

Thanks your reply. You say "Systemtap uses the literal Go symbol names as C identifiers". But SystemTap 2.8 release say it support golang. It does do any adapting work for golang application? I cannot find more information for this. Do you know any up to date information for this? 在 2017年9月19日星期

[go-nuts] Why http header letter case changes?

It is true that http header keys are case-nonsensitive. Then why the letter case gets changed inside "*http.Response"? An "ETag" header added and in the response we had "Etag" (the letter T converted to lowercase). I've encountered this when doing some testing and this behavior was unpleasant

Re: [go-nuts] Does golang support SystemTap well?

Thanks your reply. As I known, `pprof` only can tell your which function is busy on cpu, memory allocated/in-use and so on. But It cannot tell you a function latency/elapsed, how long we wait on a mutex. Is there any plan to add more feature in pprof ? 在 2017年9月19日星期二 UTC+8下午9:27:31，Ian Lance T

Re: [go-nuts] tagging releases of x/crypto

On Tue, Sep 19, 2017 at 9:36 AM, 'Peter Moody' via golang-nuts wrote: > > We're big consumers of the x/crypto packages, but the lack of semantic > versioning tags means that our dependency management tools can easily > pull in incompatible versions when we update. > > what would it take to start t

Re: [go-nuts] signal.Notify + exec.CommandContext + cancel = erratic results

Yes! That was what I needed - thanks! Art Mellor : a...@priestlyemus.com : 414-678-9011 On Tue, Sep 19, 2017 at 2:51 PM, Tamás Gulácsi wrote: > ``` > <-ctx.Done() > err := ctx.Err() > ``` > just before printing out the error. > > 2017. szeptember 19., kedd 20:02:50 UTC+2 időpontban Art Mello

Re: [go-nuts] signal.Notify + exec.CommandContext + cancel = erratic results

Spoke too soon - if you make cancelTimeout bigger than sleepDur, it doesn't end after sleepDur, it blocks until the cancelTimeout fires. I'm going to stew on this some more. Art Mellor : a...@priestlyemus.com : 414-678-9011 On Tue, Sep 19, 2017 at 3:20 PM, Art Mellor wrote: > Yes! That was

[go-nuts] Got questions about Functional Programming?

If so, read this: https://lexsheehan.blogspot.com/2017/09/characteristics-of-functional.html p.s. An older version of the same article will be published soon in Packpub's Article Network. -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsu

Re: [go-nuts] signal.Notify + exec.CommandContext + cancel = erratic results

One additional data point. If I add the following line right after 'r.cmd.Run()' in RunMe.Run, it works: time.Sleep(1 * time.Nanosecond) It seems that the context error takes a moment to be filled in properly... -- You received this message because you are subscribed to the Google Groups

[go-nuts] http2 issues with Safari 9 and 10 and EventSource

I am encountering an issue with Safari 9 and Safari 10 when using Event Source (server sent events) and http2. The browser opens the connection, immediately closes the connection, and then attempts to reconnect. This repeats in an infinite loop, flooding the server with requests. I was able to

[go-nuts] Re: Go : Philosophy

You might find Go Proverbs and the related video by Rob Pike interesting. On Monday, June 28, 2010 at 9:43:48 AM UTC-4, Mayuresh Kathe wrote: > > Like the UNIX philosophy (below); > Write programs that do one thing and do it well. > Write programs to

[go-nuts] tagging releases of x/crypto

hey folks, We're big consumers of the x/crypto packages, but the lack of semantic versioning tags means that our dependency management tools can easily pull in incompatible versions when we update. what would it take to start tagging releases of x/crypto? Cheers, peter -- You received this mes

[go-nuts] Go tool for formatting sql in the source code

Start by building a lexer for your SQL dialect or find an existing one. Once done investgate the go/ast package. -- 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

Re: [go-nuts] Does golang support SystemTap well?

> I don't know why Go programs would not work with systemtap. Because when tracing function call returns systemtap installs trampolines in the return address slots. This confuses traceback, which doesn't expect systemtap functions in the stack trace. It also breaks stack frame copy for the same re

Re: [go-nuts] signal.Notify + exec.CommandContext + cancel = erratic results

On Tue, Sep 19, 2017 at 7:22 AM, Art Mellor wrote: > > I have a program that is working on my Mac reliably, but gives erratic > results on other (linux) systems. It maybe something wrong with my code, > but it not obvious to me at all what I might have done wrong. Have you run your program unde

Re: [go-nuts] Does golang support SystemTap well?

On Tue, Sep 19, 2017 at 1:50 AM, wrote: > ENV : > SystemTap version : 3.1/0.160 > Linux kernal : 3.10.0-229.el7.x86_64 > Golang : 1.8.3 > > Recently, I use SystemTap to do some tracing for a golang application. But > it occurred many fatal error, e.g: > > SIGILL: illegal instructio

[go-nuts] Re: Computing the number of days between two dates...

The solution has a bug when b has the year higher than a. In my project I use a solution based on the Julian Day. More about this you can read here: http://en.wikipedia.org/wiki/Julian_day On Wednesday, October 21, 2015 at 3:34:51 PM UTC+3, Karthik Krishnamurthy wrote: > > This is an old post,

[go-nuts] Does golang support SystemTap well?

ENV : SystemTap version : 3.1/0.160 Linux kernal : 3.10.0-229.el7.x86_64 Golang : 1.8.3 Recently, I use SystemTap to do some tracing for a golang application. But it occurred many fatal error, e.g: SIGILL: illegal instruction PC=0x7fffe015 m=41 sigcode=2 ... SIGTRAP: trace t

[go-nuts] need a mentor for a charity taskrabbit.com

dear goers, we had a thought with a friend about creating an open sourced *clone of taskrabbit.com* website concept but for people in need, as a *charity* work. my experience is limited to (*assembly/c *long time ago), more currently python and learning atm *html/css/js* roadpath. i would l

Re: [go-nuts] Doing "C-like" things in Go

On 11 September 2017 at 17:56, CampNowhere wrote: > I am a C developer and am trying to pick up Go. > > My question is this. C doesn't "care" about truthfulness, it just cares > about zero and non-zero when evaluating a logical AND operator. So something > like the following in C is totally kosher

[go-nuts] Re: ListenAndServeTLS() godoc comment

According to RFC4346 (found via serverfault ), the root certificate can optionally be omitted from the PEM file. So sending the root CA along with the rest of the trust chain seems unnecessary but not wrong. On Tuesday, September 19, 2017 at 12:25:46 PM UTC+2,

[go-nuts] Re: ListenAndServeTLS() godoc comment

Reading the certs file in a loop is fine. However, the godoc comment should IMHO say, that the cert file should only consist of the server certificate and the intermediate certificate(s) but NOT the root CA certificate. On Tuesday, September 19, 2017 at 11:43:49 AM UTC+2, Christoph Berger wrote:

[go-nuts] Re: ListenAndServeTLS() godoc comment

My fault, I misinterpreted the diagram on Wikipedia. You are right, the root CA would not have to be sent to the client then. When I visit the source of ListenAndServeTLS and drill down the function calls that receive the cert file as a parameter, I end up at function X509KeyPair (Sourcegraph.c

[go-nuts] Re: Suggestions about reusing function/method information in comments, swagger, logs, events

Hi Brunetto, While I don't have "a take and go" solution, I have some thoughts to discuss. What I like about swagger and openapi is the ability to abstract the way you describe your API's, from the particular implementation. This paradigm is (almost) perfectly matches to Go's code generation p