As of CL 817742, go1.26.0 is this module's minimum toolchain version.
For golang/go#72774.
[git-generate]
find . -type f -name 'Dockerfile' -exec sed -i '' 's/golang:1.25/golang:1.27/' {} +
Thanks.
This is expected because `go mod vendor` vendors package code, but it doesn't include _test.go files. Those live only in the upstream packages. See https://pkg.go.dev/cmd/go#hdr-Make_vendore…
Thanks.
Yep, it's a [property](https://cs.opensource.google/go/x/build/+/master:internal/gophers/gophers.go;l=42-45;drc=d955bf84b4b91d638eba901cbc7e01722e79fa98) of the interal/gophers package that …
(1 comment)
Has it already been considered to reuse one of the existing ones (e.g., https://golang.org/x/build/gerrit or https://pkg.go.dev/github.com/andygrunwald/go-gerrit), and decided that the t…
(1 comment)
Tests seem to pass with it, and it's also there in the upstream CL 797560, so it should be fine for the backport CL to be consistent with that. (But it can probably be removed on the mai…
(1 comment)
DeleteBranch is a better fit for DestructiveGerritClient, isn't it?
(If you'd like to change it but it's a bit disruptive this early in the stack, note that it's also fine to defer to e…
Thanks for making this suggestion too. Updated [CL 783580](https://go.dev/cl/783580) to mention this issue.
https://go.dev/wiki/Deprecated is clear that deprecating an exported symbol requires a pro…
(2 comments)
This change is ready for review.
Hold for #80795.
Will use issue #80795. We can make it a proposal and discuss whether to also to deprecate at the same time as adding these go:fix inl…
Thanks.
https://go.dev/s/style#declaring-empty-slices suggests:
> When designing interfaces, avoid making a distinction between a nil slice and a non-nil, zero-length slice, as this can lead to sub…
(1 comment)
Note that I would expect you'll need to add a " (optional)" suffix to the parameter name in order for relui to permit the empty string input, since it's that's the zero value of string. …
Thanks.
In my quick testing on a moderately representative machine, `go test -count=1 -short cmd/go/...` went from around 24 seconds to around 30 seconds, which seems very reasonable.
Is it intenti…
We approved this backport request fairly early on after the Go 1.26.0 release, but the issue is still not resolved at tip. Closing this backport issue for now, and once the upstream issue is resolved…
We approved this backport request fairly early on after the Go 1.26.0 release, but the issue is still not resolved at tip. Closing this backport issue for now, and once the upstream issue is resolved…
> is there anything else needed for this issue
There are 3 tests in net/http that are currently skipped that [point to this issue](https://cs.opensource.google/search?q=%22go.dev%2Fissue%2F67555%22&…
(1 comment)
Note that this command is marked as deprecated, so if running that command causes some problem there'd be no good path forward without migrating off that command. Since proposal #71859 i…
(2 comments)
[sort.Slice](https://pkg.go.dev/sort#Slice) documentation includes:
> Note: in many situations, the newer [slices.SortFunc](https://pkg.go.dev/slices#SortFunc) function is more ergonom…
Note that it's also possible to try a newer version that includes the fix by using its pseudo-version, such as `v0.49.1-0.20260813165158-3c18a2d52646`, ahead of its includion in the next release tag …
Issue #80220 is resolved, and openbsd-ppc64-n2vi is back online and [green](https://ci.chromium.org/ui/p/golang/g/port-openbsd-ppc64/builders). Thanks. Closing.
Issue #80220 is resolved, and openbsd-ppc64-n2vi is back online and [green](https://ci.chromium.org/ui/p/golang/g/port-openbsd-ppc64/builders). Thanks. Closing.
Thanks.
Yeah, I think the 1.24 release notes is a better place to add this note. After some time passes, most people looking to learn what changed in it would be looking there rathe than in 1.27 rel…
Marking as resolved (per discussion in other thread). There are still some failures on https://ci.chromium.org/ui/p/golang/builders/ci/gotip-plan9-amd64, but that can be tracked in a followup to #636…
Made the [second pre-release tag](https://pkg.go.dev/github.com/go-gl/glfw/v3.4/glfw@v0.1.0-pre.2) to include some of the follow up fixes to v3.4/glfw. If some time passes and there aren't problems r…
Thanks for preparing this. Closing since this change needs to happen upstream. Note that by now v3.4 has superseded v3.3, so it may make sense to redirect our attention towards the latest version in …
Thanks for preparing this. Closing since this change needs to happen upstream. Note that by now v3.4 has superseded v3.3, so it may make sense to redirect our attention towards the latest version in …
One more note. In the PR description it was mentioned that this change was done with `go mod edit -go=1.26`. In most cases it should be a better experience to manage the `go` directive with the `go g…
Thanks, this generally looks good. I left two minor comments.
I suggest picking `1.26.0` for the `go` directive here.
Prior to Go 1.21, major releases didn't have a ".0" at the end. See https://go.…
Sounds good, thanks.
If someone wishes to use an older version of go-gerrit before its `go` directive increased for a while longer, even if you don't tag, they could still use the corresponding ps…
> Go 1.27.0 is the current upstream release, so the supported window moves to 1.27 + 1.26 per the [Go Release Policy](https://go.dev/doc/devel/release.html#policy) the README commits to. [...] The `g…
(2 comments)
This isn't quite right. According to the spec, the optional [init statement](https://go.dev/ref/spec#InitStmt) is a [simple statement](https://go.dev/ref/spec#SimpleStmt), which in addi…
(1 comment)
At least in Go 1 package documentation it was a documented bug that gave the heads up that the behavior may change in a future version:
https://pkg.go.dev/encoding/json@go1#pkg-note-BUG
How does this compare with CL 812781?
This looks good too, just please coordinate with Michael. Thanks.
For #80818? Or is there another tracking issue for these perf builders?
See https://go-revie…
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…
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 …