Re: [go-nuts] How can I identify the default value of the -p build flag?

Thanks. That confirms that Go thinks there are 36 CPUs available in that environment. I'm still a bit surprised that there's no way to invoke the go executable to get the value of runtime.NumCPU. A quick grep through src/cmd looks like it isn't directly exposed anywhere. I might file an issue requ

Re: [go-nuts] How can I identify the default value of the -p build flag?

On Fri, Nov 2, 2018 at 2:29 PM, wrote: > > This is somewhat an XY problem, so let me preface with the X: > > We infrequently see `/usr/local/go/pkg/tool/linux_amd64/link: signal: > killed` when running `go test` for our project on CircleCI, running Go > 1.11.1. > > As far as I can tell, that kill

[go-nuts] Re: Go 1.11.2 and Go 1.10.5 are released

I updated my release related resources: - Go Release Timeline - When Should You Upgrade Go? On Friday, November 2, 2018 at 3:06:58 PM UTC-7, Andrew Bonventre wrote: > > Hello gophe

[go-nuts] Go 1.11.2 and Go 1.10.5 are released

Hello gophers, We have just released Go versions 1.11.2 and 1.10.5, minor point releases. View the release notes for more information: https://golang.org/doc/devel/release.html#go1.11.minor You can download binary and source distributions from the Go web site: https://golang.org/dl/ To

[go-nuts] How can I identify the default value of the -p build flag?

This is somewhat an XY problem, so let me preface with the X: We infrequently see `/usr/local/go/pkg/tool/linux_amd64/link: signal: killed` when running `go test` for our project on CircleCI, running Go 1.11.1. As far as I can tell, that killed signal is due to OOMing. The comment at https://g

[go-nuts] Re: Go2 Error Handling Feedback

Your example code is missing 4 error checks that should additionally be handled. On Thursday, 1 November 2018 11:17:37 UTC+2, Henry wrote: > > Hi, > > I am concerned with the direction Go2 is going. If anything, Go2 should > reduce and consolidate features from Go1 rather than adding new ones.

Re: [go-nuts] Re: Large (binary or text) File transfers over rpc

Moving files is a solved, non trivial problem Have you looked at tools like scp (ssh), rsync, kermit, ftp, sftp, tftp and network filesystems (nfs and samba)? Even git and http. Error recover, host name lookup, compression, restart, safe abort, transport encryption, authentication, buffering.

[go-nuts] Can any one build successfully shared library linked against shared std?

I'm trying to build simplest library in `shared` mode linked against shared std. Ubuntu 18.04 , go 1.11.1 installed with godeps. $ sudo rm /usr/local/go/pkg/linux_amd64_dynlink/ -rf $ sudo rm ~/.cache/go-build/ -rf $ sudo go install -buildmode=shared std $ mkdir ~/go/src/mylibrary $ cat > ~/go/