go, branch go1.23rc1

[release-branch.go1.23] go1.23rc1

2024-06-21T16:32:19Z

Change-Id: Ied4bb63f49d13bd7d421cf9cb269220974641b89 Reviewed-on: https://go-review.googlesource.com/c/go/+/593897 Auto-Submit: David Chase Reviewed-by: David Chase Reviewed-by: Dmitri Shuralyov LUCI-TryBot-Result: Go LUCI Auto-Submit: Gopher Robot

[release-branch.go1.23] internal/godebugs: fix old value for httpservecontentkeepheaders

2024-06-20T19:14:07Z

The pre-Go 1.23 behavior is httpservecontentkeepheaders=1. For #66343 Change-Id: If6f92853b38522f19a8908ff11ac49b12f3dc3e0 Reviewed-on: https://go-review.googlesource.com/c/go/+/593775 Reviewed-by: David Chase Auto-Submit: Damien Neil LUCI-TryBot-Result: Go LUCI Reviewed-on: https://go-review.googlesource.com/c/go/+/593795 Reviewed-by: Damien Neil Reviewed-by: Michael Pratt

[release-branch.go1.23] cmd/compile: support generic alias type

2024-06-20T19:13:52Z

Type parameters on aliases are now allowed after #46477 accepted. Updates #46477 Fixes #68054 Change-Id: Ic2e3b6f960a898163f47666e3a6bfe43b8cc22e2 Reviewed-on: https://go-review.googlesource.com/c/go/+/593715 Reviewed-by: Robert Griesemer Reviewed-by: Matthew Dempsky LUCI-TryBot-Result: Go LUCI Auto-Submit: Robert Griesemer Reviewed-on: https://go-review.googlesource.com/c/go/+/593797 Reviewed-by: Michael Pratt

[release-branch.go1.23] internal/syscall/unix: fix UTIME_OMIT for dragonfly

2024-06-20T19:13:34Z

CL 219638 added UTIME_OMIT values for various systems. The value for DragonFly BSD appears to be incorrect. The correct value is -2 (see references below), while -1 is used for UTIME_NOW. As a result, timestamp is changed to the current time instead of not touching. This should have been caught by the accompanying test case, TestChtimesWithZeroTimes, but its failures are essentially skipped on dragonfly (this is being fixed separately in a followup CL 591535). Improve formatting while at it. References: - https://github.com/DragonFlyBSD/DragonFlyBSD/blob/965b380e9609/sys/sys/stat.h#L284 - https://go.googlesource.com/sys/+/refs/tags/v0.20.0/unix/zerrors_dragonfly_amd64.go#1421 Change-Id: I432360ca982c84b7cd70d0cf01d860af9ff985fa Reviewed-on: https://go-review.googlesource.com/c/go/+/589496 LUCI-TryBot-Result: Go LUCI Reviewed-by: Cherry Mui Auto-Submit: Ian Lance Taylor Reviewed-by: Ian Lance Taylor Commit-Queue: Ian Lance Taylor Reviewed-on: https://go-review.googlesource.com/c/go/+/593796 Reviewed-by: Michael Pratt

[release-branch.go1.23] update codereview.cfg for release-branch.go1.23

2024-06-18T21:25:28Z

Change-Id: Ib335bc903e2b8d5b7be6a158a6debe5db48e79a4 Reviewed-on: https://go-review.googlesource.com/c/go/+/593535 LUCI-TryBot-Result: Go LUCI Auto-Submit: David Chase Reviewed-by: Michael Pratt

net/http: keep Content-Encoding in Error, add GODEBUG for ServeContent

2024-06-18T19:33:10Z

This reverts the changes to Error from CL 571995, and adds a GODEBUG controlling the changes to ServeContent/ServeFile/ServeFS. The change to remove the Content-Encoding header when serving an error breaks middleware which sets Content-Encoding: gzip and wraps a ResponseWriter in one which compresses the response body. This middleware already breaks when ServeContent handles a Range request. Correct uses of ServeContent which serve pre-compressed content with a Content-Encoding: gzip header break if we don't remove that header when serving errors. Therefore, we keep the change to ServeContent/ ServeFile/ServeFS, but we add the ability to disable the new behavior by setting GODEBUG=httpservecontentkeepheaders=1. We revert the change to Error, because users who don't want to include a Content-Encoding header in errors can simply remove the header themselves, or not add it in the first place. Fixes #66343 Change-Id: Ic19a24b73624a5ac1a258ed7a8fe7d9bf86c6a38 Reviewed-on: https://go-review.googlesource.com/c/go/+/593157 Reviewed-by: Russ Cox LUCI-TryBot-Result: Go LUCI

doc/next: update release notes for go list -m -json

2024-06-18T19:07:25Z

For #65614 Change-Id: I49921aefb79efbc012e745cc2abd9ff36c0a9149 Reviewed-on: https://go-review.googlesource.com/c/go/+/593495 Reviewed-by: Dmitri Shuralyov Auto-Submit: Sam Thanawalla LUCI-TryBot-Result: Go LUCI Reviewed-by: Dmitri Shuralyov

all: update vendored golang.org/x/tools

2024-06-18T18:48:10Z

Pull in CL 593297: f2d2ebe4 go/analysis/passes/buildtag: retire Go 1.15 support Along with other changes that have landed into x/tools. This fixes a vet failure reported on longtest builders. For #66092. Change-Id: I549cc3f8e2c2033fe961bf014ff8cc1998021538 Cq-Include-Trybots: luci.golang.try:gotip-linux-amd64-longtest Reviewed-on: https://go-review.googlesource.com/c/go/+/593376 Reviewed-by: Dmitri Shuralyov TryBot-Bypass: Dmitri Shuralyov Reviewed-by: David Chase Auto-Submit: Dmitri Shuralyov

doc/next: add release notes for telemetry and the godebug directive

2024-06-18T17:57:51Z

For #65614 Change-Id: I6274bdaba970cfb085af500fdaf8ed078202bfdc Reviewed-on: https://go-review.googlesource.com/c/go/+/591380 Reviewed-by: David Chase Reviewed-by: Russ Cox Reviewed-by: Dmitri Shuralyov LUCI-TryBot-Result: Go LUCI

misc/ios: rework exec wrapper to only support simulator

2024-06-18T16:32:49Z

This updates the tools used to execute Go binaries on the Apple iOS Simulator to (a) work with newer arm64 macOS, (b) remove support for running binaries on physical devices, and (c) remove the reliance on LLDB and third-party Python packages. This makes the wrapper somewhat simpler, and easier to understand and maintain. Additionally clangwrap.sh is updated to reflect dropping support for targeting physical devices. This smoothes out the path for #66360. Change-Id: I769127e65f5e8c6c727841168890fd8557fb0e1d Reviewed-on: https://go-review.googlesource.com/c/go/+/573175 Reviewed-by: Michael Knyszek LUCI-TryBot-Result: Go LUCI Reviewed-by: Cherry Mui