(1 comment)
Hmm, I should've put that code in a block that so the Markdown string doesn't render in the Gerrit comment view. π
```
fmt.Sprintf("TODO: accepted [proposal %d](/issue/%[1]d)", num)
β¦
Thanks for doing this. A couple suggestions I was thinking about, since you're already planning to improve this to handle link generation better. I'll review after that.
I'm not sure I understand thβ¦
Thanks.
FWIW, I tried looking a bit into how doc comment linking can be used when brackets are involved, and found it may be viable to do some linking.
That is, it is possible, though it does mean β¦
@prattmic noticed and reported in https://github.com/golang/go/issues/79733#issuecomment-4575506443 that the cmd/api tool missed encoding/json/v2 API changes. It may be related to the API being gatedβ¦
Thanks for preparing this release note.
The doc/next files in this repo were deleted in CL 784700. The process of filing the API audit issue (#79733) and merging the release note fragments into x/weβ¦
Thanks. I think this is good to merge as soon as the trybot failure is fixed. The improved format will make it easier to many people to follow up in parallel on addressing the TODOs, so no need for tβ¦
> One caveat, seems like go mod tidy doesn't delete the empty go.sum file...
Ah, yeah. Maybe that's solvable with a 4th line like:
```
//go:generate rm go.sum # workaround for go.dev/issue/36236
`β¦
(1 comment)
This note was intentionally added as regular text for readers, rather than deprecating the symbol, to avoid creating churn.
Now that go:fix inline can reduce the toil in migrating from β¦
Thanks for working on this, and sorry about the review latency. In general, this looks good and makes sense. Thanks for implementing all the steps involved in tagging and following up.
I left a numbβ¦
It's good that you're taking into account that there is a general-purpose tagging workflow in relui (I was going to mention it in CL review too). That said, that workflow is intended to work on all oβ¦
Thanks.
This makes sense to me. My one minor comment is about possibly simplifying the probe configuration a bit, but I have no objections to any of it if it helps.
From briefly re-reading about hoβ¦
This PR is being closed because [go.dev/cl/234660](https://go.dev/cl/234660) was closed.
The x/build/gerrit [package comment](https://pkg.go.dev/golang.org/x/build/gerrit#pkg-overview) is now moreβ¦
This PR is being closed because [go.dev/cl/234660](https://go.dev/cl/234660) was closed.
The x/build/gerrit [package comment](https://pkg.go.dev/golang.org/x/build/gerrit#pkg-overview) is now moreβ¦
This should be covered at https://go.dev/wiki/MinorReleases. In particular, see this paragraph:
> When the child issue is labeled CherryPickApproved, the original author of the change fixing that isβ¦
It's preferable to be able to run the TestRelease/rc test ahead of the
upcoming RC 1 release, and see that it passes. Make that possible with
a fairly small scope reduction in the FakeCloudBuild implβ¦
> as far as I know that is not considered an "API change" and so no proposal needed
I prepared CL 783580 but became less sure about that. After all, a similar argument may apply - adding a go:fix inβ¦
I suspect it may work to make GO111MODULE=on work by taking advantage of go:generate directives being defined to execute in a predictable order, and doing something like:
```
//go:generate go get goβ¦
(Someone may extend that argument to say that it's odd to accept an error return from example and test functions, but not from net/http [handlers](https://pkg.go.dev/net/http#Handler).)
(1 comment)
This change is ready for review.
(nit) This should maintain a trailing newline. A self-reminder to remember to push a patch set with a fix.
This is before the fix. The test case passes, but it's exhibiting the
buggy behavior. The next CL implements a fix and updates the test case
to require intended behavior.
The test case defines a vcsβ¦
@prattmic Do you happen to have a link to the build handy? I tried looking over the last few https://ci.chromium.org/ui/p/golang/builders/luci.golang.ci/gotip-linux-amd64-noopt and didn't spot this fβ¦
Thanks.
I left a comment at https://go.dev/issue/79676#issuecomment-4557824015 on a similar issue. It seems to apply to issue #79677. The test is passing at the tip commit of the main branch. But maβ¦
@4a6f656c Should we take the next steps towards removing the known issue for this builder, so that it starts to shows up at https://ci.chromium.org/p/golang/g/go-gotip/console instead of only appeariβ¦
Generated with updatestd, though it's equivalent to manually running:
cd src/cmd
go get golang.org/x/tools@internal-branch.go1.26-vendor # v0.39.1-0.20260527181557-0f52e3809b35
go mod tidy
go mod vβ¦
The failures seem to be commits on the dev.simd branch, prior to it being merged into the main branch. The merge conflict that was resolved at https://go-review.googlesource.com/c/go/+/782083/4/src/gβ¦
The failures seem to be commits on the dev.simd branch, prior to it being merged into the main branch. The merge conflict that was resolved at https://go-review.googlesource.com/c/go/+/782083/4/src/gβ¦
We should avoid suggesting a fix if the needle or predicate may
have side effects. Otherwise, the program behavior may change.
For example, in converting from a loop to slices.ContainsFunc,
the needlβ¦
(2 comments)
Are there still tests that fail when running 'go test os' on Windows without an administrator account after this change? If not, this can become Fixes, otherwise Updates is fine.
The nβ¦
Copied votes on follow-up patch sets have been updated:
* Code-Review+2 has been copied to patch set 2 (copy condition: "is:ANY").
(3 comments)
For golang/go#64169.
Though I guess by now that issuβ¦
I think it's a good idea to add //go:fix inline directive, and as far as I know that is not considered an "API change" and so no proposal needed. But deprecating symbols does need a proposal. Up to yβ¦
Thanks.
This was a minimal change to get the test working at tip. It was only afterwards that I realized the entire 1.17 codepath and the test are made obsolete by the go.mod file's go 1.25.0 directβ¦
I initially left a π reaction, but have since removed it. I mistakenly thought this package's scope was only to cover the transition period, but it turns out there's more. The commit message of [β¦
This module has a go directive set to 1.25.0. Some of the files have
build constraints that will therefore never be satisfied, such as the
'//go:build !go1.18' constraint in the typeparams_go117.go fβ¦
TestAPIConsistency correctly reports at Go tip that String methods
on the TypeList, TypeParamList, and Instance types are inconsistent.
They were added in Go 1.27 as part of proposal go.dev/issue/792β¦
(1 comment)
This link is missing a leading '/', causing it to break.
```suggestion
contexts where a generic function is [assigned](/ref/spec#Assignability) to a
```
Thanks.
[CL 775981](https://go.dev/cl/775981) added a local counter for the target port GOOS/GOARCH, and [CL 776000](https://go.dev/cl/776000) enabled its uploading for Go 1.27+. We should start seβ¦
Thanks.
[CL 775981](https://go.dev/cl/775981) added a local counter for the target port GOOS/GOARCH, and [CL 776000](https://go.dev/cl/776000) enabled its uploading for Go 1.27+. We should start seβ¦
Some of the lines were indented by 2 spaces, some by 4. Make them all
indented by a single tab, and the viewers can use their preferred tab
width in their text editor. This is based on gofmt using a β¦
Closing since this hasn't happened in a while. [CL 588235](https://go.dev/cl/588235) may have helped (or will help for next time it flakes.) Watchflakes will reopen or file a new issue as needed.
Closing since this hasn't happened in a while. [CL 588235](https://go.dev/cl/588235) may have helped (or will help for next time it flakes.) Watchflakes will reopen or file a new issue as needed.
@gri@golang.org Since you are the author of this change, and self-review in this repository is not allowed, it would be better to leave a +1 vote with your @google.com account rather than +2. This alβ¦
The Go 1.27 code freeze has recently started. This is a time to update
all golang.org/x/... module versions that contribute packages to the
std and cmd modules in the standard library to latest masteβ¦
Pull in the latest published version of github.com/google/pprof
as part of the continuous process of keeping Go's dependencies
up to date.
For #36905.
[git-generate]
cd src/cmd
go get github.com/goβ¦
[CL 767441](https://go.dev/cl/767441) generated a preliminary list for Go 1.27. It's the same list as for Go 1.26 except the macOS minimum version became 13, and that's noted at https://tip.golang.orβ¦
@alexbrainman Your understanding above about longtest builders is right. Only builders with the "longtest" runtime modifier run `go test` without `-short` flag. All other builders run `go test -shortβ¦
This sounds like a useful automatic behavior. It would help make existing CLs (or lack thereof) easier to see, and it would reduce some of the toil involved in [issue gardening](https://go.dev/wiki/Gβ¦
I agree that -author:gopherbot is probably a reasonable way to filter out such issues. Still, since the Automation label exists and its description matches, watchflakes might as well use it.
Note thβ¦