Activity

Today
dmitshur closed an issue cmd/go/internal: fix copy paste error56m
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…
Yesterday
CC @golang/release, @cherrymui.
dmitshur commented on cmd/go/internal: fix copy paste error17h
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…
dmitshur closed an issue golang.org/x/crypto: cut a new release18h
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…
linux-arm passed in patch set 3. Temporary hold while release branches are frozen for https://groups.google.com/g/golang-announce/c/8tdz5l-ccTs.
linux-arm passed in patch set 2. Temporary hold while release branches are frozen for https://groups.google.com/g/golang-announce/c/8tdz5l-ccTs.
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…
CC @ianlancetaylor, @neild, @nicholashusin.
CC @golang/command-line.
dmitshur commented on encoding/xml: unrecognized failures1d
CC @golang/mips.
Yes, this month's 'Tag x/ repos' relui workflow (#48523) is running this week, and it will tag the next golang.org/x/crypto version.
Other than that one failure, gotip-linux-amd64_c4dh96-perf_vs_release has been green, so closing again.
This Week
CC @golang/release, @thatnealpatel.
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…
A temporary hold for after Go 1.27 RC 3 is out.
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…
This issue seems to be the same as #77482. Merging them into one.
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.
dmitshur fixed an issue all: the tree is highly flaky1d
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…
Closing as fixed by [CL 794541](https://go.dev/cl/794541) per https://github.com/golang/go/issues/49929#issuecomment-1883911440.
> 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…
@roland@golang.org Pinging this since it seems close to submission, if that's still your plan here, and may have gotten lost. Thanks.
Last Week
(2 comments) s/usersn/users/ Is the block comment above still up to date?
This change has already been applied via CL 804523.
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…
Earlier
Fixed by [CL 567136](https://go.dev/cl/567136).
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.
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…
Closed by merging [CL 807680](https://go.dev/cl/807680) (commit d5eeaa7de337f01173036096619cba09e31bde1a) to release-branch.go1.27.
(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 …
Retrying trybots since "stream error: stream ID 11; INTERNAL_ERROR" may not happen a second time.
(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.…
Reopening to track [cherry-picking](https://groups.google.com/g/golang-dev/c/jMWTCiV0aSk/m/Qo6ozI0dBQAJ) [CL 804062](https://go.dev/cl/804062) onto release-branch.go1.27.
This may be the same issue as #75031, which is fixed by now. @zccold, does this still reproduce for you with go1.27rc1+, or go1.26.3 or 1.25.10?
@nicholashusin Please be aware that without a milestone set, the release-blocker label doesn't block any particular Go release.
@dsnet Please be aware that without a milestone set, the release-blocker label doesn't block any particular Go release.
@hardikmodha Both the freeze exception and backports to Go 1.26 and 1.25 are actively being considered. See https://github.com/golang/go/issues/80516#issuecomment-5071611439. @gopherbot Please open…
It's documented at https://pkg.go.dev/cmd/go@go1.27rc2#hdr-Test_packages that: > As part of building a test binary, go test runs go vet on the package and its test source files to identify significa…
(1 comment) Please consider adding “Fixes #75143.” here. Or “For” if you think there’s more left to do after this.
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…
dmitshur commented on doc: write release notes for Go 1.273w
@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.
Fixed by [CL 801520](https://go.dev/cl/801520).
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…
Thanks. ```suggestion func getContainer(ctx context.Context) (_ *Container, err error) { start := time.Now() ```
(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…
Which release is this a blocker for? (This issue currently has no Milestone, making the release-blocker label a no-op.)
dmitshur reviewed +2 on all: update vendored dependencies3w
Thanks.
dmitshur commented on all: update vendored dependencies3w
(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.
dmitshur commented on all: update vendored dependencies3w
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.
Letting this land for Go 1.28. Thanks.
Trybot failure looks like #76901, retrying it.