As far as I can tell, the swarming bot code hasn't been updated to be compatible with Python 3.14 yet, and you're among the first to notice and report this. I see that `pkgutil.get_loader` call is st…
It’s documented at https://pkg.go.dev/cmd/go#hdr-Build_constraints - search for “amd64.v3” as the exact name of the build tag, not “GOamd64.v3”; the GO prefix is a part of the environment v…
(1 comment)
I removed it to improve readability of this code. The blank line doesn’t seem helpful. Without the blank line, it’s clear that the value of security is computed to be one of web.Secu…
@stefanb It was noted in https://go.dev/doc/go1.25#json_v2, back when the encoding/json/v2 package started its experimental phase, that its design would evolve. I imagine users who have been experime…
Thanks.
I think some of the fixes by default leave code in a way that its readability can be improved when considering the context. I left some minor suggestions.
The variable name "before" is very…
(4 comments)
https://go.dev/doc/contribute#commit_messages suggest to "Write in complete sentences with correct punctuation, just like for your comments in Go." It's probably fine not to even mentio…
Thanks.
Because of the mandatory '/', this will exclude failures in the top-level TestServeIndexHtml test itself. Maybe it's more common to want to match the test and all its subtests too? If so, co…
Thanks.
I'll also add an optional x_build-gotip-linux-amd64 trybot here so we can see what it reports.
https://go.dev/wiki/CommitMessage#reverts suggests including the CL number.
```suggestion
Thi…
It's not a problem for x/build itself, since we generally use stable Go releases there, so no worries there. It's good that it was able to uncover this.
Depending on how much other code this problem…
At tip, starting with [CL 701299](https://go.dev/cl/701299), building the [golang.org/x/build/internal/relui](https://golang.org/x/build/internal/relui) package has started to fail with:
```
FAIL go…
(1 comment)
I'd expect this version to get maintained, but you may have not picked up the absolute latest updatestd. It's fine since it'll happen in a future run too.
The bootstrap on the builders should be go1.26.0 as of CL 801200. There's also been a small updatestd update recently, so consider rebasing and regenerating. I also left a suggestion about git-genera…
(1 comment)
```suggestion
For golang/go#76975.
Change-Id: Ibc508c39eb4785515d98b4eaf4fce299831b4924
```
So that this CL shows up in the timeline of that proposal.
Thanks.
This seems like a reasonable approach. I'll note that since we're dealing with HTML and Markdown and CSS and differently sized devices here, I also anticipate there's some chance of this lea…
(1 comment)
This change is ready for review.
Tested via a shadow bucket build at https://ci.chromium.org/b/8676172686530536289. It's based on the real build https://ci.chromium.org/b/86761811769047…
Thanks.
Thanks for suggesting astutil.Apply - though I knew about the existence of that package, I hadn't used it in a long while and didn't think to look there when implementing this. I did conside…
@nsrip-dd Please note https://go.dev/s/release#july--january-week-3-work-on-the-next-release-begins:
> During this period, fixes intended for the current release need to be [cherry-picked onto the r…
(3 comments)
In the main Go repo, the "src" path element is normally left out, so that the path is closer to the actual import path of the relevant Go package.
```suggestion
cmd/go/internal/doc: al…
(1 comment)
This parent commit is a bit old, before the fix for #80212 landed, so that particular test will fail. Rebasing would resolve that, otherwise we can bypass if that's the only failing test.
(1 comment)
I checked locally that this works with a generic method (that @mpratt@google.com originally reported this with), and it does work as expected:
```
$ go vet -stdversion
main.go:7:19: ran…
Thanks.
I understand this test case, in contrast to the one above, captures the case where it's not a valid version but it does have a valid version as a substring. It seems like a good idea to add …
We removed the release-blocker label since there doesn't seem to be anything actionable left that would block the release. This issue will stay open to track any further refinement and improvement le…
The existing formatting completely forgot to include the
type name T in the name of a field or method pkg.T.name.
Since this cannot be derived from a field *types.Var, we
change TooNewStdSymbols to …
Thanks. 2026c landed in time for Go 1.27.0. It's likely the last tzdata release to be included, so moving this to the next milestone. (If another tzdata release happens with some time before 1.27.0, …
Thanks.
Do you have an opinion on whether an assertion like this should go into test code (i.e., in a _test.go file) or the package implementation code? I have a slight preference for placing these …
Thanks. There are some gopls tests that aren't passing yet.
Is you preference to include this in 1.27's vet output too, or do you think this might be too risky or disruptive and better to leave to G…
It looks like this isn't a regression related to generic methods, rather it's how this check displays methods in general:
<img width="568" height="293" alt="Image" src="https://github.com/user-attac…
@prattmic Thanks. Factored that out into #80363 since it might be more involved, and updated this to be about the more general problem of cmd/vet not being aware of all new-to-1.27 symbols.
For golang/go#38706.
For golang/go#80360.
[git-generate]
go run golang.org/dl/go1.27rc2@latest download
go run golang.org/dl/go1.27rc2@latest generate ./internal/stdlib
For golang/go#38706.
For golang/go#80360.
[git-generate]
go run golang.org/dl/go1.27rc1@latest download
go run golang.org/dl/go1.27rc1@latest generate ./internal/stdlib
(1 comment)
Sounds good. Given we have agreement, we can move in that direction. It can happen independently of this change though, so added it as a TODO comment for now.
Thanks.
Note that this non-nil error is also being returned to the caller to be handled. Adding a log line here will cause it to be double-logged, see line 185.
The new log line includes scanner.Te…
Thanks.
Does it help for this to use $TAG too?
```suggestion
docker run --name=sandbox_dev --rm --network=sandnet -ti -p 127.0.0.1:8080:80/tcp -v /var/run/docker.sock:/var/run/docker.sock golang/p…
Thanks. One more comment in Workflow.Run, otherwise I don't see anything more from my side, and I think you should feel free to submit this and/or try it out. As with any new workflow, trying it out …
Thanks.
```suggestion
module crypto/internal/fips140/sha3/_asm
```
Unrelated to this CL, but I wonder what is the motivation for this go.mod? Usually they're used to track tools used for code gener…
Both the -racegocommand and -racegocommand-noopt builders have been running for some time, and so far they haven't uncovered interesting races in the go command. Issue #79667 turned out to be a probl…
(1 comment)
A question related to this. As far as I see, TOOLEXEC_CDRIVER_LOG is only used to by this test in one way: to point it to a cdriver.log file and then later on check under cgo that it doe…
See https://ci.chromium.org/ui/p/golang/builders/ci/gotip-netbsd-arm64/b8676812685865790769/overview for example. (A different test fails on Plan 9, see #80319.)
CC @golang/netbsd.
We got by with increasing memory available to coordinator. By now it no longer does builds itself, only displays an old-style dashboard [build.golang.org](https://build.golang.org) pointing to [LUCI …
Thanks for implementing this.
I left some review comments. In general, this looks like a good start, and when the comments are resolved we should be able to submit this.
Two suggestions here.
One,…
Thanks.
Since this CL is a part of what's needed, you might want to keep the issue open for a bit until the VMs are up and everything works as you expect.
Unless I missed it, you'll still need to d…
Thanks.
Yeah, I considered that too but stopped at just rc2 for now to match the labels that exist. For rc3 hopefully we'll really resolve all release blockers or remove the release-blocking label. …
Thanks.
I did something similar in CL 732263 earlier. It's still open because I was deciding whether to lower it a bit further before submitting. By now all legacy builds are stopped, so let's go wi…
Generated with updatestd, though it's equivalent to manually running:
cd src/cmd
go get golang.org/x/tools@internal-branch.go1.27-vendor # v0.45.1-0.20260708165844-7044391f8d9f
go mod tidy
go mod v…
Thanks. This looks okay to me so +1, though I expect there may be a better reviewer for go/analysis/passes packages. I understand this will be waiting on the proposal to be accepted anyway.
It took …
This change gets the [golang.org/x/tools/go/analysis/passes/printf.Test](https://ci.chromium.org/ui/p/golang/builders/try/x_tools-go1.27-linux-amd64-longtest/b8676896302437009505/test-results?q=Ex…
This change gets the [golang.org/x/tools/go/ssa.TestStdlib](https://ci.chromium.org/ui/p/golang/builders/try/x_tools-go1.27-linux-amd64-longtest/b8676896325792242385/test-results?q=ExactID%3Agolan…
CL 784060 updates Types.Info.Instantiations to preserve receivers
for generic methods, which breaks these tests. This change updates
a test to allow that CL to merge.
For golang/go#79657.
Fixes gola…
The `internal-branch.go1.27-vendor` branch in x/tools was created quite early after the start of the Go 1.27 release freeze, as opposed to closer to when the Go 1.27 release freeze will be ending. So…
(1 comment)
Since this is a release-branch.go1.26 backport CL, it would've been optimal if the commit message had:
```suggestion
For #79005.
Fixes #79027.
```
Then the Go1.26.5 backport issue #790…
> I investigated this issue and found that updating "pkgsiteCmdInternalDocVersion" to "v0.0.0-20260630164626-55ca6a10dee5" fixes the generic method rendering problem. I verified that "go doc -http" n…