[go-nuts] Go 1.21 Release Candidate 2 is released

Hello gophers, We have just released go1.21rc2, a release candidate version of Go 1.21. It is cut from release-branch.go1.21 at the revision tagged go1.21rc2. (An earlier revision was tagged go1.21rc1, but a bug found after tagging prevented its release process from completing.) Please try your

[go-nuts] Re: why no archive distribution for darwin 1.20.1?

The .tar.gz files are there as usual. They didn't show earlier up due to a caching bug on the download page (https://go.dev/issue/58527). Thanks for spotting this. On Tuesday, February 14, 2023 at 1:51:57 PM UTC-5 m...@xoba.com wrote: > on https://go.dev/dl/ i only see the packaged version

Re: [go-nuts] [security] Go 1.18.3 and Go 1.17.11 are released

On Wednesday, June 1, 2022 at 5:12:53 PM UTC-4 ja...@kastelo.net wrote: > On 1 Jun 2022, at 22:58, Dmitri Shuralyov wrote: > > > Hello gophers, > > We have just released Go versions 1.18.3 and 1.17.11, minor point releases. > > These minor releases include 4 security fixe

[go-nuts] [security] Go 1.18.3 and Go 1.17.11 are released

Hello gophers, We have just released Go versions 1.18.3 and 1.17.11, minor point releases. These minor releases include 4 security fixes following the security policy : - crypto/rand: rand.Read hangs with extremely large buffers On Windows, rand.Read will hang

[go-nuts] [security] Go 1.18.1 and Go 1.17.9 are released

Hello gophers, We have just released Go versions 1.18.1 and 1.17.9, minor point releases. These minor releases include three security fixes following the security policy: - encoding/pem: fix stack overflow in Decode A large (more than 5 MB) PEM input can cause a stack overflow in Decode,

[go-nuts] Go 1.18 Release Candidate 1 is released

Hello gophers, We have just released go1.18rc1, a release candidate version of Go 1.18. It is cut from release-branch.go1.18 at the revision tagged go1.18rc1. Please try your production load tests and unit tests with the new version. Your help testing these pre-release versions is invaluable.

[go-nuts] [security] Go 1.16.6 and Go 1.15.14 are released

Hello gophers, We have just released Go versions 1.16.6 and 1.15.14, minor point releases. These minor releases include a security fix according to the new security policy (#44918 ). crypto/tls clients can panic when provided a certificate of the wrong type for

[go-nuts] Go 1.17 Beta 1 is released

Hello gophers, We have just released go1.17beta1, a beta version of Go 1.17. It is cut from the master branch at the revision tagged go1.17beta1. Please try your production load tests and unit tests with the new version. Your help testing these pre-release versions is invaluable. Report any

[go-nuts] Go 1.16.3 and Go 1.15.11 are released

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

Re: [go-nuts] possible inconsistency in the embed package documentation

> Consider the case where example.com/m1/nested is not a separate module. > Due to the rule of "Patterns must not contain ‘.’ or ‘..’ path elements", the nested package can not embed, as an example, the LICENSE file from the example.com/m1 package. > The LICENSE file is not outside the nested

Re: [go-nuts] possible inconsistency in the embed package documentation

It gets pretty subtle. The ".git" directories aren't included in module zips by the go command (I don't know if this is documented anywhere, but it's very sensible behavior), but they aren't disallowed. A custom module zip may include a ".foo", "_foo", or even ".git" directory with files. In

Re: [go-nuts] possible inconsistency in the embed package documentation

Directories named testdata are included in the module; they're needed for tests to run. The most important thing that's left out are subdirectories that contain a go.mod file, since the content of such directories is a different module. Some good places to look for full details include

[go-nuts] Re: possible inconsistency in the embed package documentation

I think both are needed, they don't overlap. Note that the second phrase says "must not contain '.' or '..' path *elements*", emphasis them being a complete path element. So "./git" is disallowed by the second phrase, but ".git" is not. On Saturday, January 16, 2021 at 1:10:47 PM UTC-5

[go-nuts] Go 1.15.2 and Go 1.14.9 are released

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

[go-nuts] Go 1.14.4 and Go 1.13.12 are released

Hello gophers, We have just released Go versions 1.14.4 and 1.13.12, minor point releases. These releases include fixes to the go doc command, the runtime, and the encoding/json, go/types, math/big, and os packages. View the release notes for more information:

Re: [go-nuts] Re: Go 1.14.1 and Go 1.13.9 are released

To add to what Ian said, I've edited the issue titles now, which makes them slightly shorter and easier to read. Also see https://golang.org/doc/faq#go_or_golang. While the language is called "Go", the term "golang" still comes up occasionally in some contexts. On Thursday, March 19, 2020 at

[go-nuts] Re: godoc.org - Internal server error

Thanks for reporting. There's a GitHub issue tracking this, see https://github.com/golang/go/issues/36642#issuecomment-576044533. On Sunday, January 19, 2020 at 12:47:33 PM UTC-5, Steven Hartland wrote: > > Looks like somethings wrong with godoc.org atm, not sure who maintains > this as every

[go-nuts] godoc (golang.org/x/tools/cmd/godoc) has become module-aware

Hello gophers, godoc , the local web server that displays documentation for Go packages (not to be confused with https://godoc.org, the website), has been updated with support for Go modules. (This was issue 33655 .)

[go-nuts] Go 1.13 is released

Hello gophers, We just released Go 1.13. You can read the announcement blog post here: https://blog.golang.org/go1.13 You can download binary and source distributions from our download page: https://golang.org/dl/ To compile from source using a Git clone, update to the release with

[go-nuts] Go 1.12.9 is released

Hello gophers, We have just released Go version 1.12.9, a minor point release. This release includes fixes to the linker, and the os and math/big packages. View the release notes for more information: https://golang.org/doc/devel/release.html#go1.12.minor You can download binary and source

[go-nuts] [security] Go 1.12.8 and Go 1.11.13 are released

Hi gophers, We have just released Go 1.12.8 and Go 1.11.13 to address recently reported security issues. We recommend that all users update to one of these releases (if you’re not sure which, choose Go 1.12.8). - net/http: Denial of Service vulnerabilities in the HTTP/2 implementation

[go-nuts] Go 1.12.6 and Go 1.11.11 are released

Hello gophers, We have just released Go versions 1.12.6 and 1.11.11, minor point releases. These releases include fixes to the compiler, the linker, the go command, and the crypto/x509, net/http, and os packages. View the release notes for more information:

[go-nuts] Go 1.12 Beta 2 is released

Hello gophers, We have just released go1.12beta2, a beta version of Go 1.12. It is cut from the master branch at the revision tagged go1.12beta2. Please try your production load tests and unit tests with the new version. Your help testing these pre-release versions is invaluable. Report any

[go-nuts] [security] Go 1.11.3 and Go 1.10.6 are released

Hi gophers, We have just released Go 1.11.3 and Go 1.10.6 to address three recently reported security issues. We recommend that all users update to one of these releases (if you’re not sure which, choose Go 1.11.3). - cmd/go: remote command execution during "go get -u" The issue is

[go-nuts] Re: [security] Go 1.11.3 and Go 1.10.6 pre-announcement

(12 pm PST, 3 pm EST). Thanks, Dmitri on behalf of the Go team On Fri, Dec 7, 2018 at 2:08 PM Dmitri Shuralyov wrote: > Hello gophers, > > We plan to issue Go 1.11.3 and Go 1.10.6 on Wednesday, December 12 at > approximately 8 pm UTC (12 pm PST, 3 pm EST). These are minor relea

[go-nuts] [security] Go 1.11.3 and Go 1.10.6 pre-announcement

Hello gophers, We plan to issue Go 1.11.3 and Go 1.10.6 on Wednesday, December 12 at approximately 8 pm UTC (12 pm PST, 3 pm EST). These are minor releases to fix a security issue. Following our policy at https://golang.org/security, this is the pre-announcement of those releases. Thanks,

[go-nuts] Go 1.11 Beta 3 is released

Hello gophers, We have just released go1.11beta3, a beta version of Go 1.11. It is cut from the master branch at the revision tagged go1.11beta3. Please try your production load tests and unit tests with the new version. Your help testing these pre-release versions is invaluable. Report any

[go-nuts] Re: All the Go project history, live in RAM

Brad, another question. I've read the documentation at https://godoc.org/golang.org/x/build/maintner/godata, but it doesn't make it clear: is it safe/supported to have more than 1 process on one machine call godata.Get and use returned maintner.Corpus at the same time? I know each call uses

[go-nuts] Re: yaml 1.1 release

Just as a heads up, this package (gopkg.in/yaml.v2) is now also affected by issue https://github.com/niemeyer/gopkg/issues/54. It wasn't one of the affected import paths a week ago. On Friday, February 23, 2018 at 2:20:22 PM UTC-5, Roger Peppe wrote: > > Of course I mean 2.1. Version two. TWO

[go-nuts] Re: New to Go; Saying Hello !

Hello! I can really relate to what you're describing. When I started programming in Go 5 years ago, I felt the same way, and I still do to this day! There are so many moments of joy and bliss that happen when working with it daily. :) Hope you continue to enjoy it too! On Friday, February

Re: [go-nuts] net/http: Redirect writes HTML for GET requests without setting Content-Type, how come?

Quick followup note here. The CL that resolves this issue has been merged, and should be a part of Go 1.10 release. On Saturday, July 22, 2017 at 11:46:40 PM UTC-4, Dmitri Shuralyov wrote: > > Thanks Matt, that corroborates with my understanding too. > > I've sent a C

Re: [go-nuts] net/http: Redirect writes HTML for GET requests without setting Content-Type, how come?

*really* old! > So the Content-Type should be set as if responding normally to a GET > request. I think Redirect should be setting Content-Type (perhaps only if > it's not already set?). > > On Tue, Jul 18, 2017 at 8:41 PM Dmitri Shuralyov <shur...@gmail.com > > wrote: &

[go-nuts] net/http: Redirect writes HTML for GET requests without setting Content-Type, how come?

I've written a little middleware to help catch instances where I write some content in an HTTP handler, but forget to set the Content-Type header. I prefer to always set it to avoid forcing the browser to guess. It feels good and produces more predictable results. I've noticed some of my

[go-nuts] Re: [ANN] githubql—a client library for accessing GitHub GraphQL API v4

Wow, it would probably help if I linked to the actual package (although it seems Google-able from the name alone): https://github.com/shurcooL/githubql On Wednesday, May 31, 2017 at 3:55:13 PM UTC-4, Dmitri Shuralyov wrote: > > This package is very new, I've just created it a few da

[go-nuts] [ANN] githubql—a client library for accessing GitHub GraphQL API v4

This package is very new, I've just created it a few days ago after a week of research and prototyping. Feedback is welcome. If you're interested in the details of its design evolution and the various approaches I've considered, I wrote a lengthy comment at

[go-nuts] Re: go1.8 and json.NewDecoder(resp.Body)

Relevant: https://github.com/google/go-github/pull/317 See the discussion and the CLs to Go std lib that Brad sent out as a result. On Tuesday, May 23, 2017 at 8:34:03 AM UTC-4, John Shahid wrote: > > Hi all, > > Some background, we (CloudFoundry) noticed some weird behavior after > upgrading

[go-nuts] Re: All the Go project history, live in RAM

Another small question. https://godoc.org/golang.org/x/build/maintner#GerritProject.Server says: > Server returns the Gerrit server, such as "go.googlesource.com". I thought that go.googlesource.com was a Gitiles server, and go-review.googlesource.com is where the Gerrit server is (according

[go-nuts] Re: All the Go project history, live in RAM

> > The data is generally under 1 second behind reality, thanks to the > webhook+incoming-SMTP server we run now at https://pubsubhelper.golang.org/ > to get updates from GitHub & Gerrit. > Just a quick implementation question related to that. I understand you use Webhooks to get data from

[go-nuts] Re: Building with "go install" vs "go build"

> > Are there more that I'm unaware of? > go get. It downloads source and follows it up with go install. Are some preferred in certain circumstances > The three ways you listed are similar but not equivalent, they have subtle differences in behavior. Use whatever is a better fit for your

[go-nuts] Re: $GOPTAH/bin and $PATH

Yes, it is. As far as I know, everybody does it and/or expects you to. Unless you have some specific reason not to. On Thursday, February 2, 2017 at 5:31:32 AM UTC-5, adrian...@hushmail.com wrote: > > Gophers, > > Is it idiomatic to add $GOPTAH/bin to $PATH in order access a Go > executable

[go-nuts] Re: OS X Installer: Why modify $PATH instead of adding symbolic links to /usr/local/bin?

> > Can someone please explain the thinking behind this design decision? Is it > more common on Linux to have a lot of path additions instead of symbolic > links to executables? Was this something that was discussed and decided > upon by the core team or just an arbitrary decision? > I'd

[go-nuts] Re: WebAssembly as a target

I would be very interested in this. I think GopherJS has shown how compelling it can be to be able to write Go that can run in the browser. It serves as a great preview of that ability, enabling one to experiment and prototype things. But to really get the best performance, minimum file size,