> I'm surprised there isn't a failing test.
I suspect current test didn't catch a bad `pkgsiteCmdInternalDocVersion` constant value because it overrides the real pkgsite binary and its version with …
runtime:mayMoreStackMove.TestCoroLockOSThread/CoroLockOSThreadStopLockedIterNested failed on linux-arm64-longtest, otherwise everything passed. That failure is unrelated to this change.
By now PRIVATE-track security fixes involving a vendored package
have been released, and these tests can be made to run again.
For #80765.
For #80767.
[git-generate]
updatestd -goroot=$(pwd) -branc…
By now PRIVATE-track security fixes involving a vendored package
have been released, and these tests can be made to run again.
For #80744.
For #80745.
[git-generate]
updatestd -goroot=$(pwd) -branc…
Enforce a recursion limit in Unmarshal to prevent stack exhaustion when
parsing deeply-nested, recursive structures.
Thanks to Marwan Atia (marwansamir688@gmail.com) for reporting this
issue.
Fixes…
Closed by merging [CL 811000](https://go.dev/cl/811000) (commit cafd3448c7cb0b2d793bb4144d58f72ef3f48327) to release-branch.go1.25.
CC @golang/release, @mrkfrmn.
Closed by merging [CL 811000](https://go.dev/cl/811000) (commit cafd3448c7cb0b2d793bb4144d58f72ef3f48327) to release-branch.go1.25.
CC @golang/release, @mrkfrmn.
Closed by merging [CL 811020](https://go.dev/cl/811020) (commit 33ecb966ca47e55034272a9146e23e9909507f6d) to release-branch.go1.26.
CC @golang/release, @mrkfrmn.
Closed by merging [CL 811020](https://go.dev/cl/811020) (commit 33ecb966ca47e55034272a9146e23e9909507f6d) to release-branch.go1.26.
CC @golang/release, @mrkfrmn.
> I'm under the impression that to participate in the minors, this needs backports.
Indeed, all minor release fixes need a corresponding backport issue. In addition to tracking, the backport issues …
As far as I can tell, this wasn't intended to be added the Go1.26.5 milestone since it has no CherryPickCandidate label nor "[1.26 backport]" suffix in title, and it doesn't seem to fixed at tip yet.…
Thanks for the information. Since [CL 762500](https://go.dev/cl/762500) didn't have an issue associated, I filed #80850 for it retroactively and used it for the backport.
@gopherbot Please consider this for backport to Go 1.26. There's a semi-workaround available by using `CXXFLAGS` to control Fortran flags, but that can only be used if C++ flags aren't needed, and a …
https://pkg.go.dev/cmd/cgo#hdr-Using_cgo_with_the_go_command documents the behavior:
> CFLAGS, CPPFLAGS, CXXFLAGS, FFLAGS and LDFLAGS may be defined with pseudo #cgo directives within these comments…
Please see https://go.dev/wiki/MinorReleases for the backport process.
We'll need more information to consider a backport request, anything that would help us understand why a backport might be warr…
Thanks.
Consider requiring at least one builder that's running into this, e.g.:
```suggestion
Change-Id: I47aed66bc30fda86366042cbf8fcc32e6a6a6964
Cq-Include-Trybots: luci.golang.try:gotip-linux-am…
One of the remaining enhancements here is to re-check for any updates to the release notes when sending the announcement, so that it'd pick up any improvements to the release notes that may happen. (…
It was noted at https://groups.google.com/g/golang-dev/c/jMWTCiV0aSk/m/Qo6ozI0dBQAJ:
> Any CLs that land after CL 800721 ("internal/goversion: update Version to 1.28") but target go1.27.0 must be ch…
Thanks.
Thanks for checking. I asked because keeping these comments up to date will help with future maintenance of this sequence, and it seemed worth some extra attention.
This part seems out of d…
Go 1.27 RC 3 will be released alongside Go 1.26/1.25 minor releases with some [pre-announced](https://groups.google.com/g/golang-announce/c/8tdz5l-ccTs) PRIVATE-track security fixes. Unfortunately, t…
Go 1.27 RC 3 will be released alongside Go 1.26/1.25 minor releases with some [pre-announced](https://groups.google.com/g/golang-announce/c/8tdz5l-ccTs) PRIVATE-track security fixes. Unfortunately, t…
Go 1.27 RC 3 will be released alongside Go 1.26/1.25 minor releases with some [pre-announced](https://groups.google.com/g/golang-announce/c/8tdz5l-ccTs) PRIVATE-track security fixes. This didn't make…
Go 1.27 RC 3 will be released alongside Go 1.26/1.25 minor releases with some [pre-announced](https://groups.google.com/g/golang-announce/c/8tdz5l-ccTs) PRIVATE-track security fixes. This didn't make…
RC 3 will be released alongside 1.26/1.25 minors with some [pre-announced](https://groups.google.com/g/golang-announce/c/8tdz5l-ccTs) PRIVATE-track security fixes. This didn't make it in time, so add…
@sunny@golang.org The description of the Code-Review submit requirement says:
> At least one Code-Review+2 is required. Self review is not allowed.
"Self review is not allowed" in this context mean…
Pinging this issue since it's very late in the [Go 1.27 release cycle](https://go.dev/s/release#timeline), and this is one of the few remaining open Go 1.27 release blockers. Is there a planned time …
I'm realizing now this is currently an open proposal. Does it still need to go through the proposal process? If so, perhaps it should be in the Proposal milestone until that's done.
@prattmic Would you like to submit that CL now that we're early in Go 1.28 development cycle? Moving this to Go1.28 milestone, otherwise feel to update it to Backlog.
There's been work to address this and I think we're no longer in the "highly flaky" state, so closing.
In general, highly flaky tests affecting [first-class ports](https://go.dev/wiki/PortingPolicy#…
It looks like there's been a good amount of progress on this issue in the Go 1.27 milestone, and it's documented at http://go.dev/doc/go1.27#runtime. This issue is still open and in the Go1.27 milest…
> I'm reopening this issue to track updating x/net/idna for older toolchains as well.
@neild Just to confirm, there's nothing actually left to change in the Go 1.27 and newer toolchains, is that rig…
Thanks.
Since this has a tracking issue (the one mentioned in the comment below), please include it here too:
For #77341.
CL 804523 is submitted by now and it makes a similar change. I'll rebase t…
It seems this particular test relies on the exact output of http.FileServer, which changed in [CL 795560](https://go.dev/cl/795560) for issue #80208:
```
$ go test -run=^TestServer_ServeHTTP//noinde…
Pull in the fixes implemented in CL 805322, CL 805520, and CL 805400.
For #80410.
For #80554.
[git-generate]
updatestd -goroot=$(pwd) -branch=internal-branch.go1.27-vendor
Thanks.
Optionally, might be more readable to use a named variable:
```suggestion
if minor := release.Patch == 0; !minor || !isVSCodeGoInsiderVersion(release, "") {
```
I see other similar code d…
Thanks.
Noting that this zero version that was here previously made the replacement directive highly load-bearing; the new version makes it more optional.
Thanks.
In general, be mindful that going from 1.21 to 1.25 will include a fair number of changes, including the scope of variables in for loops (https://go.dev/doc/go1.22#language) and others at ht…
Thanks.
Not seeing this change.
Also, what does the 'X' in `TestSelectGoDirectiveXReposLive` refer to? Previously the 'X' in `TestSelectGolangOrgXReposLive` was a part of "golang.org/x". Now that i…
(1 comment)
I see, so dropping -u and switching to `work` at once indeed doesn't work - `go get work` ends up _not_ doing `go get directdependency@upgrade` at all. Consider keeping `all` and only dr…
(7 comments)
https://go.dev/doc/contribute#commit_messages suggests "Write in complete sentences with correct punctuation, just like for your comments in Go." Perhaps:
```suggestion
This will help …
Reopening and moving to Go 1.27 milestone to track [cherry-picking](https://groups.google.com/g/golang-dev/c/jMWTCiV0aSk/m/Qo6ozI0dBQAJ) [CL 807700](https://go.dev/cl/807700) onto release-branch.go1.…
@mrkfrmn This issue is in Go1.18 milestone, and it's also frozen/locked due to age. Maybe it's better to file a new one and reference this old issue? (Otherwise we should move it to a future mileston…
(1 comment)
Since that issue was reopened and updated to track the Go1.27 fix, this could say "Fixes" instead of "Updates" so the issue will get automatically closed when this lands. It's also fine …
(1 comment)
I think you might want to consider `go get work` instead of `go get -u all` here.
The -u flag means to update not only the direct dependencies of the specified packages, but also their …
Reopening and moving to Go 1.27 milestone to track [cherry-picking](https://groups.google.com/g/golang-dev/c/jMWTCiV0aSk/m/Qo6ozI0dBQAJ) [CL 803320](https://go.dev/cl/803320) onto release-branch.go1.…