Activity

Today
Thanks. I don't mind seeing a note like this in a code review comment, but I'm not sure about including it in the commit message itself. Perhaps this is still a topic being discussed and I may chang…
(4 comments) Consider making this commit message much shorter, focusing on the problem being surfaced by the Go 1.26 vet check (#72850). For example, compare with similar CLs for x/sys and x/exp: CL…
Yesterday
As suggested at https://go.dev/issue/80220#issuecomment-5350598333, it can be helpful to say a few more words about the exact Python 3 version that should be used. Also, an optional reference, point …
It's not very visible on the issue, but as of today it does have a pending code change (https://crrev.com/c/8265616).
CL 763260 moved some of this code; rebased in PS 2.
It's caught by Go 1.26's vet check that the format %q here is given a wrong type int. The formatting verb %d is appropriate.
Unfortunate timing of my reply with Commit-Queue... Bypassing trybots since they did pass on patchset 1.
It's caught by Go 1.26's vet check that the format %q here is given a wrong type uint16. Convert it to a rune instead.
Thank you! Yes, proposal #69095 was about having a policy and automation to maintain the minimum value of the `go` directive in golang.org/x modules, and this CL is a part of that, but it's possible…
Closed by merging [CL 815220](https://go.dev/cl/815220) (commit 983064c1b5bd8e0ad581607aa140167c698cd4eb) to release-branch.go1.25.
With the release of [Go 1.27.0](https://go.dev/doc/go1.27), the two supported major Go releases are 1.27 and 1.26 per the [Go release policy](https://go.dev/doc/devel/release#policy). Closing this 1.…
With the release of [Go 1.27.0](https://go.dev/doc/go1.27), the two supported major Go releases are 1.27 and 1.26 per the [Go release policy](https://go.dev/doc/devel/release#policy). Closing this 1.…
With the release of [Go 1.27.0](https://go.dev/doc/go1.27), the two supported major Go releases are 1.27 and 1.26 per the [Go release policy](https://go.dev/doc/devel/release#policy). Closing this 1.…
With the release of [Go 1.27.0](https://go.dev/doc/go1.27), the two supported major Go releases are 1.27 and 1.26 per the [Go release policy](https://go.dev/doc/devel/release#policy). Closing this 1.…
With the release of [Go 1.27.0](https://go.dev/doc/go1.27), the two supported major Go releases are 1.27 and 1.26 per the [Go release policy](https://go.dev/doc/devel/release#policy). Closing this 1.…
With the release of [Go 1.27.0](https://go.dev/doc/go1.27), the two supported major Go releases are 1.27 and 1.26 per the [Go release policy](https://go.dev/doc/devel/release#policy). Closing this 1.…
With the release of [Go 1.27.0](https://go.dev/doc/go1.27), the two supported major Go releases are 1.27 and 1.26 per the [Go release policy](https://go.dev/doc/devel/release#policy). Closing this 1.…
With the release of [Go 1.27.0](https://go.dev/doc/go1.27), the two supported major Go releases are 1.27 and 1.26 per the [Go release policy](https://go.dev/doc/devel/release#policy). Closing this 1.…
Tentatively closing this as a duplicate, but please comment here or in issue #70698 if there's still an issue.
@xcolwell I believe support for type aliases in x/mobile was already added as of [CL 740861](https://go.dev/cl/740861), so the temporary workaround of setting GODEBUG manually in the environment shou…
I found [go.dev/cl/804720](https://go.dev/cl/804720) that matches this description, is that what you're referring to? If so, the issue in that CL is that it's on the main branch, so it needs to use "…
@srinivas-pokala Thanks for reporting this. Can you please include links to where you ran into this? One possibility is that the builder names and repository branch names are out of alignment. In th…
As visible on the build dashboard¹² and reported in go.dev/issue/80703, the power8 builders are gone. Annotate them with a known issue to hide some purple boxes from the build dashboard, making it …
Delete code that became dead as of CL 818140. Generated files unchanged.
This change is ready for review.
Add this file now that it's possible to preview the release notes draft at https://tip.golang.org/doc/go1.28. For golang/go#80959.
dmitshur opened an issue doc: write release notes for Go 1.2814h
This is the tracking issue for writing the Go 1.28 Release Notes. The version at tip can be viewed at https://tip.golang.org/doc/next. When we have a fairly complete release notes draft, enough for …
The Go 1.27.0 release is out, so 1.26 is the oldest supported release.¹ The previous infrastructure (cmd/coordinator) does this automatically, whereas here I authored this CL manually. We'll explore…
Thanks. Since by now a stable version of Go 1.27 is also available and should work as well as Go 1.26 and better, you could go to it directly. Its other advantage is that it'll be supported for 6 mo…
Thanks.
This change is ready for review.
Thanks. One optional comment. Hmm, I noticed that in [Go 1.24 release notes](https://go.dev/doc/go1.24) and older this was linked. I'm not sure why 1.25 onwards stopped doing it, and I wonder if may…
This package has been deprecated, tagged, and deleted as part of #59056.
This package has been deprecated, tagged, and deleted as part of #59056.
Hello, I see that the README at https://github.com/gophers-latam/go-tour-es#%EF%B8%8F-reportar-issues already points to this issue tracker for issues with the Spanish translation of the Go tour. How…
This Week
(1 comment) I see - apologies about the false positive 😅 and thanks for already taking this into account.
(1 comment) In future commit messages, please consider this commit message suggestion from https://go.dev/wiki/CommitMessage: > when referencing CLs, prefer saying “CL nnn” or using a go.dev/cl…
@thiagomowszet@gmail.com Is there an issue tracker that can be used to report issues related to the Spanish translation of the tour at https://go-tour-lat.appspot.com/ ? The 'submit feedback' button …
Other than a URL, this is an empty issue without any of the needed details.
Other than a URL, this is an empty issue without any of the needed details.
That other option is what [CL 815220](https://go.dev/cl/815220) does if I understand correctly.
(1 comment) Is it expected that `go mod tidy` seemingly undoes this change (because the newly added requirements are only indirectly used)? This repo seems to use go-git/v5.
Patchset 3 passed all trybots, except go1.25-wasip1-wasm_wasmtime failed in time package due a timeout. It doesn't seem related, and it passed on second try, so adding bypass.
Moved this back to Go1.27.1 milestone to reflect today's discussion in a release meeting.
This looks related to issue #80484. It already has backport CLs in progress at [CL 812920](https://go.dev/cl/812920) and [CL 812920](https://go.dev/cl/812920), can you please check if those are enoug…
I'm not sure if retrying trybots will help. This passed on all trybots other than gotip-plan9-amd64 itself, but gotip-plan9-amd64 has a still-open known issue #63600 and it hasn't been green at https…
@Jorropo Are you referring to the fix in [CL 737880](https://go.dev/cl/737880) that was reverted (in [CL 794180](https://go.dev/cl/794180))? If so, that fix originally fixed issue #77153, and that is…
CC @golang/security, @golang/release.
Thanks. We'll stop very soon, after Go 1.27.0 is released. But that indeed hasn't happened quite yet.
I see both invitations have been accepted, so this should be done. Please comment if something got missed. Thanks.
I see both invitations have been accepted, so this should be done. Please comment if something got missed. Thanks.
Thanks. Please consider adding a reference to issue #80843 here. That way it may be easier to find if someone needs to. ``` For golang/go#80843. ```
This passed on most builders; the few failure are due to unrelated 500s from Gerrit rather than the change content.
Thanks. Do you know if having GOAMD64=v3 set in the environment will be enough and propagate to the rest of the perf tooling, without being cleared away for a consistent performance benchmarking sta…
Thanks for your work on maintaining the GOARCH=s390x port. @kmvijay-IBM and @prophet6250 should now have invitations to join the @golang/s390x team.
CC @golang/release, @golang/s390x.
Your golang.org account should work now.
Thanks. Something to consider: a "release" team doesn't exist either, but we kept the GitHub team behind and repurposed it to be, as it's currently described: > Members of this team are notified vi…
(1 comment) Something like this, perhaps: ```suggestion var validateRe = regexp.MustCompile(`^[a-zA-Z0-9(),=/_:;.-|]+$`) ```
(1 comment) Oh, is the newly permitted '|' meant to go before the '$' (end of string)?
dmitshur deleted branch in github.com/mdempsky/unconvert3d
go-126-125
(1 comment) ```suggestion Fixes golang/go#80907 ```
(2 comments) This works, but given version.Compare exists, we could replace the entire versionLess helper with it. So, please delete versionLess entirely, and in the places that currently use versi…
Thanks. From a [quick search](https://cs.opensource.google/search?q=%22The%20Go%20Authors.%20%20All%20rights%20reserved.%22&sq=&ss=go), there may be a few more repos like x/arch, x/debug, x/perf tha…
Using too old of an x/tools version causes newer toolchains such as go1.27rc3 to run into errors like 'internal error: package "strings" without types was imported'. Updating to a newer x/tools versi…
Last Week
POSIX says you follow the symlink, but some platforms don't. Add OpenBSD to the list of ones that don't. For #80386. Fixes #80888.
POSIX says you follow the symlink, but some platforms don't. Add OpenBSD to the list of ones that don't. For #80386. Fixes #80889.
POSIX says you follow the symlink, but some platforms don't. Add OpenBSD to the list of ones that don't. Fixes #80386.
This is already fixed for Go 1.28 by [CL 800700](https://go.dev/cl/800700), but it still happens on release branches. @gopherbot Please consider this for backport. It's a small OpenBSD-only change t…
Done in patchset 4. Fix applied.
Thanks. I find this description a little unclear since it doesn't say which bytes. My current understanding is that the /connect-ssh HTTP handler first writes an HTTP response to the POST request, …
@rhysh made a suggestion to consider sending an email to golang-dev to notify Go developers at tip when the PRIVATE-track security fixes have finished landing. Adding a note here since this would be …
This issue is currently in the Unreleased milestone, meaning it's only associated with the golang.org/x/net module and not the main Go release cycle. Is it expected that the fix will be inside the x/…
Done. We decided this is okay for go1.27.0.
Minor release is done, dropping hold. This backport CL is ready, but CL 812920 still needs a review.
Minor release is done, dropping hold.