Re: [go-nuts] HTTP timeout per handler

Hi Nitin, but how about making the timeout longer thant the default? For example having a general write timeout of 1 minute but allowing a certain user to download a large file for 30 min. El mar., 1 oct. 2019 a las 6:31, Nitin Sanghi () escribió: > Santiago, you can use context to cancel the

Re: [go-nuts] missing $GOPATH

Filed https://golang.org/issue/34628 On Fri, 2019-09-27 at 15:19 +0930, Dan Kortschak wrote: > Looking into it it appears that there's active work in > go/build.defaultGOPATH that makes returning an informative error > message impossible. > > This made sense when it was done in 428df5e39c0[1],

Re: [go-nuts] A confusion on the cgo document.

On Mon, Sep 30, 2019 at 1:01 AM T L wrote: > > https://golang.org/cmd/cgo/#hdr-Passing_pointers > > When passing a pointer to a field in a struct, the Go memory in question is > the memory occupied by the field, not the entire struct. When passing a > pointer to an element in an array or slice,

Re: [go-nuts] Golang library for - ORM & Schema Migration

Thank you all. For schema migration i am looking for similar tool like flyway. , Regards, Bram. On Sunday, September 29, 2019 at 2:34:55 AM UTC-7, Space A. wrote: > > ORM is a tool. It's not good or bad. Every tool, every language and > everything has limits. If you like spending time on

[go-nuts] Go policy does not fully support previous release

I was startled to learn that regressions found in the previous release (currently 1.12.x) will not be fixed in that release. Regressions are only fixed in the most recent release. If you wait until 1.12.5 to upgrade a deployment from 1.11.x, and then discover a regression on the day 1.13 comes

Re: [go-nuts] go 1.13 won't compile

Robert, It's probably worth a careful look at https://github.com/golang/go/wiki/Modules#recent-changes and https://golang.org/doc/go1.13#modules as well as Marcin's suggestion to run go env. When I do the latter, I get GO111MODULE="" GOPRIVATE="" (among many other variables but those are probably

Re: [go-nuts] go 1.13 won't compile

I hope this helps.  I removed the GO111MODULE=off that I added the other day to get compilation to work. GOARCH="amd64" GOBIN="" GOCACHE="/home/rob/.cache/go-build" GOENV="/home/rob/.config/go/env" GOEXE="" GOFLAGS="" GOHOSTARCH="amd64" GOHOSTOS="linux" GONOPROXY="" GONOSUMDB="" GOOS="linux"

Re: [go-nuts] go 1.13 won't compile

Could you post the output of "go env" run on linux mint? Maybe there's a clue in there. On Mon, Sep 30, 2019 at 9:14 AM Robert Solomon wrote: > Then my question becomes, what's different about linuxmint 19.2 to require > me to set GO111MODULE=no > > On Mon, Sep 30, 2019, 11:06 AM Everton

Re: [go-nuts] go 1.13 won't compile

Then my question becomes, what's different about linuxmint 19.2 to require me to set GO111MODULE=no On Mon, Sep 30, 2019, 11:06 AM Everton Marques wrote: > Your code from playground compiled fine for me on Debian Linux. > Tested with Go 1.13 and 1.13.1. > > Just had to include the missing func:

[go-nuts] HTTP timeout per handler

Using the http package, timeouts are defined per server. Is there any way of changing it for a specific handler? Imagine a long download from a loged user or a websocket but also be protected against clients that don't close connections and fload the server. -- You received this message

[go-nuts] Re: Migrating Google App Engine Go app to Go 1.12

"> On Monday, September 30, 2019 at 5:33:34 AM UTC-4, Jan Mercl wrote: > > Hi list. > > The modernc.org domain go-get redirector is hosted at the Google App > Engine and provides access to all packages found at this time at > https://gitlab.com/cznic. Go code for the redirector iself is >

Re: [go-nuts] go 1.13 won't compile

Your code from playground compiled fine for me on Debian Linux. Tested with Go 1.13 and 1.13.1. Just had to include the missing func: func GetUserGroupStr(f os.FileInfo) (string, string) { return "foo", "bar" } Em segunda-feira, 30 de setembro de 2019 11:34:52 UTC-3, Robert Solomon

Re: [go-nuts] go 1.13 won't compile

Your experience matches mine when compiled on windows 10. But linuxmint experience is as I described. Another responder asked me if it works when I set GO111MODULE=no. It does work when I do that. I find it interesting that the linux behavior seems to be different On Mon, Sep 30, 2019, 9:17

Re: [go-nuts] go 1.13 won't compile

FWIW, I copied your code from Go Playground into ~/go/src/dsrt/dsrt.go on my OS X machine. I replaced an undefined function at line 375 (see below) with direct assignments for usernameStr and groupNameStr. It compiled (with go build) and ran without reporting an error under go 1.13. //

[go-nuts] [ANN] Rain: BitTorrent client and library

I would like to announce the BitTorrent client I wrote. It is the main client used at https://put.io, the cloud storage company that I work at. We are using it on production for several months. You can use it as a command line tool or as a library. https://github.com/cenkalti/rain

[go-nuts] Re: causal profiling in Go

That's interesting, thanks for sharing. Also interested to know if someone got results with a similar approach. > -- 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

[go-nuts] causal profiling in Go

Hi everyone, does someone has experience with causal profiling in Go? (see http://www.sigops.org/sosp/sosp15/current/2015-Monterey/printable/090-curtsinger.pdf if you are not aware of that topic) Please note that I am aware of https://morsmachine.dk/causalprof but I want to hear a few more

[go-nuts] Re: Migrating Google App Engine Go app to Go 1.12

On Mon, Sep 30, 2019 at 11:32 AM Jan Mercl <0xj...@gmail.com> wrote: Panic mode off. Deployed, seems to work: https://gitlab.com/cznic/modernc/commit/96339947ba67960ae5bd19b625b2816fdcc7af6e Thanks to anyone who have read the OP. -- You received this message because you are subscribed to the

Re: [go-nuts] Migrating Google App Engine Go app to Go 1.12

On Mon, Sep 30, 2019 at 12:34 PM Matthew Zimmerman wrote: > > My notice said that apps continue to run, you just can't deploy new versions. > > "Starting on October 1, 2019, as per our deprecation policy, you will no > longer be able to deploy new versions of App Engine Standard applications >

Re: [go-nuts] Migrating Google App Engine Go app to Go 1.12

My notice said that apps continue to run, you just can't deploy new versions. "Starting on October 1, 2019, as per our deprecation policy , you

[go-nuts] Migrating Google App Engine Go app to Go 1.12

Hi list. The modernc.org domain go-get redirector is hosted at the Google App Engine and provides access to all packages found at this time at https://gitlab.com/cznic. Go code for the redirector iself is published at https://gitlab.com/cznic/modernc. The instance dashboard shows a warning: "A

[go-nuts] Re: Can’t get latest package version with modules

Solved the issue with the command: go get -u github.com/XXX/go-YYY@latest Is there another way ? Le lundi 30 septembre 2019 11:01:17 UTC+2, Christophe Meessen a écrit : > > I have a small go program to test a third party package stored on github. > I’m using go1.13.1 with no GOPATH

[go-nuts] Re: Can’t get latest package version with modules

Note that the third party package has no tags. Le lundi 30 septembre 2019 11:01:17 UTC+2, Christophe Meessen a écrit : > > I have a small go program to test a third party package stored on github. > I’m using go1.13.1 with no GOPATH defined. Code is in ~/go/src. > > When I first tried to

[go-nuts] Can’t get latest package version with modules

I have a small go program to test a third party package stored on github. I’m using go1.13.1 with no GOPATH defined. Code is in ~/go/src. When I first tried to compile the program, there was an error in the third party package. I submitted a pull request to fix it and the manager merged it.

Re: [go-nuts] How to use .toml file to parse IP address and port to http server

Hi, I have solve the problem and it works now. Thanks. On Monday, September 30, 2019 at 11:06:20 AM UTC+3, Afriyie Abraham Kwabena wrote: > > Hi, > > I have applied similar scenario to the function below but am not getting > the Ip address and the port number. Below is the function > > var

Re: [go-nuts] How to use .toml file to parse IP address and port to http server

Hi, I have applied similar scenario to the function below but am not getting the Ip address and the port number. Below is the function var addr string func init(){ var conf Config if _, err := toml.Decode("config.toml", ); err != nil { // handle error } addr =

[go-nuts] A confusion on the cgo document.

https://golang.org/cmd/cgo/#hdr-Passing_pointers When passing a pointer to a field in a struct, the Go memory in question is the memory occupied by the field, not the entire struct. When passing a pointer to an element in an array or slice, the Go memory in question is the entire array or the