(2 comments)
Consider doing the same change here. If you prefer to leave it for a future CL instead, that's fine too.
Not for this CL, but noting that another potential future simplification here i…
See an inline comment on go.mod. The rest of this change makes sense to me. Thanks for doing this.
I realize that the last time the deploy files in this repository were updated, the go directive was…
I think the sections "Why not bump on each minor release?" at [go.dev/design/69095-x-repo-continuous-go#rationale](https://go.dev/design/69095-x-repo-continuous-go#rationale) is moderately relevant. …
In addition to the 4 x/ repos already mentioned in the original issue, here are some more that also have Dockerfile and/or .yaml files that would benefit from automatic maintenance:
x/vulndb: https:…
The improvement to compression speed seems notable enough to be
worth mentioning. (Maybe it can be quantified succinctly enough
for release notes, or otherwise we can point to the issue.)
Even thoug…
@sin99xx Thanks for sending this change. As noted in https://github.com/golang/go/pull/79968#issuecomment-4684498141, it was successfully imported in Gerrit, and by now there are some review comments…
The failure above happened because package-level timeouts were reached. This was a darwin-arm64 race builder, which normally takes around 10 minutes to run on x/tools (https://ci.chromium.org/ui/p/go…
Thanks for trying out the package ahead of the release and reporting this finding. CC @golang/security.
Tentatively marking as a release blocker since this package is new to Go 1.27.
Issue #79967 reported a problem with the new code. @rolandshoemaker Is it preferable to fix forward and proceed with it for 1.27, instead of reverting and trying again for 1.28? Given it seems like a…
Thanks for reporting.
It's expected that exact gofmt formatting nuances will change over time, across major Go releases, so a check like `go fmt ./...` needs to be arranged to run with a single cons…
The test contains a comment:
```Go
// This test flakes out on some systems,
// so we'll try it a few times before declaring it a failure.
const attempts = 5
```
So it seems this failure is expected…
Thanks for the report. Please note that Go 1.24 is no longer supported per https://go.dev/doc/devel/release#policy. Does this still happen with Go 1.26/1.25 or at tip?
CC @neild.
@codyoss@google.com I suspect you intended to start the current trybots via Commit-Queue+1 (see https://go.dev/wiki/GerritAccess#running-trybots-may-start-trybots and https://go.dev/wiki/LUCI#trybots…
Thanks.
If I understand right, the plan for x/pkgsite deploys will generally be to use a stable release of Go (similar to CL 733341), or a release candidate of the soon-to-become-latest-stable relea…
Thanks for sending this change. Closing because this package is frozen and deprecated. In particular it is documented to be unmaintained except for security fixes. For security issues, please follow …
I don't think there's anything that to be done here given the package is deprecated and frozen. There isn't anyone we can add to be its reviewer. This isn't the only security issue, as noted in the d…
[golang.org/x/crypto/openpgp/elgamal](https://golang.org/x/crypto/openpgp/elgamal) is deprecated too. Its deprecation message notes:
> Deprecated: this package was only provided to support ElGamal e…
(1 comment)
The go/types and cmd/compile/internal/types2 packages are generally kept in sync. Please also apply the same change here:
```suggestion
// not permitted. Checker.funcInst must infer mi…
Thanks.
Asking to confirm my understanding.
As far as I see CL 787800 didn't make any Windows-specific changes. libExt was "so" on Windows both before and after that change. Is it case that it work…
Since we're in release freeze for Go 1.27 and this seems like a new feature, should it have wait-release hashtag added and wait for when the tree reopens for Go 1.28 development?
(1 comment)
Yeah, thanks for catching that. Normally <aaa/> would be self-closing syntax, but it seems that's not valid for a non-void element like head and it gets treated as a start tag. Fixed …
This proposal has a release-blocker label which applies to the issue's milestone, and it's currently in Backlog. Moved to Go 1.27 since I think that's what was intended, though perhaps it doesn't nee…
(1 comment)
Whoops, I forgot that CL 342610 and its attempted replacements haven't actually landed yet and this file is still written in HTML. :( Sent you CL 790480 to fix the broken link.
I noticed "[GerritBot](/wiki/GerritBot)" rendered as text rather than a
link at go.dev/doc/contribute. That happened because that file is still
written in HTML rather than Markdown. Fix it and some m…
Thanks. I left a few minor comments, otherwise this looks good.
Since this returns a boolean, and the boolean represents whether something is or isn't the case, I suggest using "reports whether" as …
Thanks for working on this. x/text was updated to Unicode 17 in CL 737404, so closing. If there's some aspect of this CL other than updating the Unicode version is still applicable, feel free to reop…
Thanks for working on this. x/text was updated to Unicode 17 in CL 737404, so closing. If there's some aspect of this CL other than updating the Unicode version is still applicable, feel free to reop…
It is possible to skip except on longtest builder, but we probably don’t want to do that because all.bash doesn’t run in longtest mode by default, so it means forgetting to regenerate that packag…
Thanks.
It's probably a no-op for rendered HTML, but it's breaking highlighting in Gerrit.
```suggestion
<!-- https://go.dev/issue/77626, https://go.dev/issue/78888 -->
```
The letter 'v' here …
I also found this while looking into the trybot failure in [CL 789800](https://go-review.googlesource.com/c/pkgsite/+/789800/comments/05bb9ce4_a90a56ca). Some testdata there happened to depend on the…
Git bisect finds that the relevant x/net commit is CL 781702. Its commit message includes:
> Instead of [... slow thing ...], sort the attributes and [... now a fast thing is viable ...]
So it seem…
The reason we have these particular custom timeouts in cmd/dist today
is because CL 120762 increased cmd/go timeout from 6 minutes to 9,
and before that CL 84235 increased cmd/go timeout from 3 minut…
Thanks.
nit: I think we spell it as one word without a space more commonly (e.g., see two instances in this file, and https://go.dev/doc/toolchain). (I realize this text was pre-existing, so this is…
This change drops the constant timeout from two packages where it's
been observed to be unhelpful. Applying this more widely is left to
subsequent changes.
For #79970.
As motivated in the commit message of [CL 504495](https://go.dev/cl/504495):
> Since go test has a default top-level timeout, individual tests don't
need to impose their own timeouts too. It's possi…
There've been a number of x/net/html changes in x/net@v0.56.0 (CC @roland@golang.org), test failures are likely related to that.
The diff seems to just be the position of the aria-label attribute, a…
DO NOT REVIEW
DO NOT SUBMIT
The compress/flate package documentation for NewWriter and NewWriterDict
notes:
> Note that the exact bytes written to w are not covered by the Go 1
> compatibility prom…
The packages.Load call needs to be able to find a driver such as the
go command, either via the GOPACKAGESDRIVER environment variable, or
failing that, by looking in PATH.
The intent of this custom test is to cover what isn't already tested
as part of the normal 'go test std cmd' sequence that all.bash runs.
It started providing duplicate signal once jsonv2 became the …
This is like linux-amd64-racegocommand-noopt, but without the noopt
modifier.
The previous linux-amd64-racegocommand-noopt builder hasn't found races
in the go command itself so far, but it ran into…
@oakad It is a valid alternative approach to put more emphasis on GOROOT and rely on relative paths to find the go command. Migrating to that would be a large change and would need a proposal, so bet…
The fix for the test is probably to propagate the PATH environment variable.
Issue #62114 is also related here. If it's viable to modify packages.Load itself to return an error if the PATH it's prov…
The gotip-linux-amd64-racegocommand-noopt builder has had a couple failures while running `go install -race cmd/go` ([complete environment details](https://logs.chromium.org/logs/golang/buildbucket/c…
The approved freeze exception for proposal #24673 (CC @rolandshoemaker) adds a new field in crypto/tls:
- `pkg crypto/tls, type ConnectionState struct, LocalCertificate [][]uint8`
- #24673
Edited…
Thanks.
At a high level, we want to avoid making the release notes seem like a canonical or only home for feature documentation; rather they aim to say what's new/changed and point to the actual und…
(1 comment)
Consider either changing this to 'Fixes' or manually closing afterwards. If there's something left to do, it's better to file individual issues. Otherwise that proposal could use a comme…
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.20260604184323-2111063761b3
go mod tidy
go mod v…
(1 comment)
Instead of directly pointing to a Gerrit URL here, let's point to the relevant section of the Go contribution guide:
https://go.dev/doc/contribute#config_git_auth
That way if some of t…
@bradfitz Was [CL 781800](https://go.dev/cl/781800) enough to fix this for Go1.27, or is this issue open because there's more to do? (Fixing x/sys can probably be tracked another way, since it's in a…
@Jah-yee Thanks for sending this change. Please see information posted in https://github.com/golang/website/pull/359#issuecomment-4317356043. I left review comments at https://go.dev/cl/770646.
Thanks for updating this entry. See inline comments for a few suggestions.
Moved the 'Fixes' line to the bottom of the commit message. Done.
Maybe it's worth it to include "v3" here too, since this…
That mentioned package has a comment in its AppendText method implementation:
```
// NOTE(anderseknert): this DOES allocate still, and while that's unfortunate,
// we'll be better off dealing with t…
This seems reasonable to me, but I defer to Michael for +2 review. I left minor suggestions in inline comments. Thanks.
It'd be good to document what this exported function does, and maybe mention t…