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

golang.org/dl/go1.21rc2@latest $ go1.21rc2 download You can download binary and source distributions from the usual place: https://go.dev/dl/#go1.21rc2 To find out what has changed in Go 1.21, read the draft release notes: https://tip.golang.org/doc/go1.21 Cheers, Dmitri and Michael for the Go team

[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 this

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

that particular git revision.) For questions about the Docker images published at https://hub.docker.com/_/golang, you'll want to contact their maintainers linked at the top of the quick reference section. It's reasonable to expect they'll show up soon now that this Go releas

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

lone, update to the release with "git checkout go1.18.3" and build as usual. Thanks to everyone who contributed to the releases. Cheers, Dmitri and Alex for the Go team -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubs

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

update to the release with "git checkout go1.18.1" and build as usual. Thanks to everyone who contributed to the releases. Cheers, Dmitri and Cherry for the Go team -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscrib

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

: https://go.dev/dl/#go1.18rc1 To find out what has changed in Go 1.18, read the draft release notes: https://tip.golang.org/doc/go1.18 Cheers, Dmitri and Heschi for the Go team -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubs

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

clone, update to the release with "git checkout go1.16.6" and build as usual. Thanks to everyone who contributed to the releases. Cheers, Dmitri, Filippo, and Alex for the Go team -- You received this message because you are subscribed to the Google Groups "golang-nuts" grou

[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 prob

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

/ To compile from source using a Git clone, update to the release with "git checkout go1.16.3" and build as usual. Thanks to everyone who contributed to the releases. Cheers, Carlos, David, Dmitri and Alex for the Go team -- You received this message because you are subscribed to the Goo

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 pac

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 th

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 https:/

[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 manlio..

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

compile from source using a Git clone, update to the release with "git checkout go1.15.2" and build as usual. Thanks to everyone who contributed to the releases. Cheers, Dmitri and Alex for the Go team -- You received this message because you are subscribed to the Google Groups &q

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

e. Cheers, Dmitri and Andy for the Go team -- 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 discuss

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 5

[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 p

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

ems, please let us know by leaving a comment on issue 33655 <https://golang.org/issue/33655>, filing a new issue <https://golang.org/issue/new?title=x%2Ftools%2Fcmd%2Fgodoc%3A+>, or replying to this thread. Thanks, Dmitri -- You received this message because you are subscribed to the Go

[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 "git

[go-nuts] Go 1.12.9 is released

distributions from the Go web site: https://golang.org/dl/ To compile from source using a Git clone, update to the release with "git checkout go1.12.9" and build as usual. Thanks to everyone who contributed to the release. Cheers, Dmitri for the Go team -- You received this messa

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

platforms. Thank you, Dmitri on behalf of the Go team -- 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

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

d build as usual. Thanks to everyone who contributed to the releases. Cheers, Dmitri for the Go team -- 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

[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 prob

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

n to release soon. We apologize for any disruption. Thank you, Dmitri on behalf of the Go team -- 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

[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 release

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

, Dmitri on behalf of the Go team -- 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. For more options, v

[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 prob

[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 th

[go-nuts] call for proposals for Goruco 2018

GORUCO 2018 is now accepting talk proposals! On Saturday, June 16th, GORUCO is celebrating its 12th convocation as NYC's premier regional software conference. It's a one-day, single-track event geared toward highly motivated and experienced developers that's been celebrated

[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 i

[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 23,

[go-nuts] pprof implementation concepts

I've put together a blog post explaining the implementation concepts behind CPU, allocation and block profilers. It is not as detailed as some of the original articles, but hopefully useful to pprof users in terms of better understanding what to expect from the data. https://stackimpact.com/bl

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 sen

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

hat don't understand redirects (must be *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 Shur

[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 redire

[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 f

[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 https://github.com/google/go-github/i

[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 f

[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 t

[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 Git

[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 needs

[go-nuts] Re: [ANN] Go Performance Playground

That's a good idea. The goal was however to make it as intuitive as possible and not so much the compatibility, since you mostly just write or copy/paste code. I've added more info about sandbox environment in the accompanying blog post. Basically the code is build with Go 1.8 and launched in a

[go-nuts] [ANN] Go Performance Playground

We've recently launched Go Performance Playground, which was inspired by the original Go Playground. It is available at https://play.stackimpact.com. Example: https://play.stackimpact.com/p/zIRPhlywKG Should be useful for quick CPU profiling, algorithm optimization and more. More information i

[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

Re: [go-nuts] $GOROOT_BOOTSTRAP variable not found if all.bash is run with sudo

sudo sanitizes environment, you need to either pass -E option or add GOROOT_BOOTSTRAP to env_keep in /etc/sudoers: Defaults env_keep += "GOROOT_BOOTSTRAP" On Sat, Dec 10, 2016 at 1:57 PM, xMudrii wrote: > Hi, > > I have downloaded Go 1.4 binaries and moved it to `/usr/local/go1.4` for > example

[go-nuts] [ANN] StackImpact - pprof-based production profiler and monitor

here", “SomeGoApp”) This starts the agent, which runs with the app from start till the end. Performance information will be reported to and available in the Dashboard at https://stackimpact.com (or on-premise respectively) Your feedback is welcome! Thanks, Dmitri -- You received th

[go-nuts] Re: goimports has been updated

> > hey brad, is it possible to have a ```goimports version``` so that we know > what versions we currently have? I suggest using the command: go get -u -v golang.org/x/tools/cmd/goimports The -v flag will print packages that are rebuilt. If the output is empty, that means you already had th

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

> > I'd love to get a better understanding of why this choice. I have never > seen another software take this approach. As I mentioned before, I'm not familiar with the original thinking, but here are some ideas on the advantages of this approach that I can see: 1. it avoids symlinks (I don't

[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 love

[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, e