Re: [go-nuts] Can someone please explain http.HandlerFunc() ?

2020-04-03 Thread Kurtis Rader
On Fri, Apr 3, 2020 at 7:10 PM joe mcguckin wrote: > I see some code like: > > r.NotFoundHandler =http.HandlerFunc(notfound) > > Where notfound() has the signature of > > func notfound(w http.ResponseWriter, r *http.Request) > > What is HandlerFunc() doing? It’s not a

[go-nuts] Can someone please explain http.HandlerFunc() ?

2020-04-03 Thread joe mcguckin
I see some code like: r.NotFoundHandler =http.HandlerFunc(notfound) Where notfound() has the signature of func notfound(w http.ResponseWriter, r *http.Request) What is HandlerFunc() doing? It’s not a function. Is it some sort of type coercion or casting? I can see

[go-nuts] random test failure of TestScript/mod_indirect in 'cmd/go'

2020-04-03 Thread 'Bryan C. Mills' via golang-nuts
Please file an issue. https://golang.org/issue/new -- 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 view this

Re: [go-nuts] http.client.Do(request) panics in highly concurrent apps (Go 1.14.1)

2020-04-03 Thread Ian Lance Taylor
On Fri, Apr 3, 2020 at 4:30 AM Robert Engels wrote: > > Sorry, got the versions wrong. Looks like the fix in 1.14.1 might need fixing. See https://golang.org/issue/38023 and https://golang.org/issue/38070. Ian > On Apr 3, 2020, at 6:12 AM, Robert Engels wrote: > >  > Which is a duplicate of

[go-nuts] Re: Pseudo version showing different in go1.12 and go1.13

2020-04-03 Thread Sean Liao
> (This was originally the only form, so some older go.mod files use this form even for commits that do follow tags.) older refers to vgo, go1.11, go1.12 On Wednesday, April 1, 2020 at 2:07:19 PM UTC+2, Nitish Saboo wrote: > > Hi, > > I created go.mod file from two different go versions 1.12

Re: [go-nuts] Re: Pseudo version showing different in go1.12 and go1.13

2020-04-03 Thread Nitish Saboo
Hi, I have already gone through this doc. The thing is I am getting two different pseudo versions for two different go versions. Are you saying I should get pseudo version v0.0.0 for both the go versions? Thanks, Nitish On Fri, 3 Apr 2020, 21:16 Sean Liao, wrote: >

[go-nuts] Re: Building yocto GO application fails with error subpackage missing

2020-04-03 Thread Tamás Gulácsi
Either dep or go modules, I think... 2020. április 3., péntek 18:44:37 UTC+2 időpontban salm...@gmail.com a következőt írta: > > I am using yocto to build a package with this recipe > > DESCRIPTION = "github.com/jackc/pgproto3" > > GO_IMPORT = "github.com/jackc/pgproto3" > > LICENSE = "MIT" >

Re: [go-nuts] Re: Pseudo version showing different in go1.12 and go1.13

2020-04-03 Thread Sean Liao
https://golang.org/cmd/go/#hdr-Pseudo_versions The note about v0.0.0 originally being the only form is relevant -- 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] Re: Pseudo version showing different in go1.12 and go1.13

2020-04-03 Thread Nitish Saboo
Hi, Can someone please guide me on this ? Thanks, Nitish On Thu, Apr 2, 2020 at 12:50 PM Nitish Saboo wrote: > Hi, > > Apologies forgot to mention, I am treying to migrate from go deps to go > modules. > Following is what is present in the Godeps for aws-sdk-go dependency > { > "ImportPath":

Re: [go-nuts] http.client.Do(request) panics in highly concurrent apps (Go 1.14.1)

2020-04-03 Thread Robert Engels
Sorry, got the versions wrong. Looks like the fix in 1.14.1 might need fixing. > On Apr 3, 2020, at 6:12 AM, Robert Engels wrote: > >  > Which is a duplicate of https://github.com/golang/go/issues/37449 > so I would comment/reopen that issue as it appears either the fix was not > correct

Re: [go-nuts] http.client.Do(request) panics in highly concurrent apps (Go 1.14.1)

2020-04-03 Thread Robert Engels
Which is a duplicate of https://github.com/golang/go/issues/37449 so I would comment/reopen that issue as it appears either the fix was not correct (unlikely since it works in 1.14) or that it wasn’t merged correctly into 1.15 (likely). > On Apr 3, 2020, at 12:20 AM, Pierre Durand wrote: > >