Activity
Yesterday
dmitshur opened a change golang.org/x/build/cmd/relui: consider target versions of security fixes in security comms7h
So far we've only had to deal with the common case where a security fix
applies to all versions that are going as part of a monthly Go release.
At some point we'll run into a case where some security…dmitshur closed a change golang.org/x/text/go.mod: update golang.org/x dependencies10h
Replaced by a newer identical CL 795500.dmitshur closed a change golang.org/x/text/go.mod: update golang.org/x dependencies10h
Replaced by a newer identical CL 795500.dmitshur commented on net: TestLookupCNAME failures10h
@gopherbot Please consider this for backport. It's a test-only fix needed to get this test passing on release branches.
CC @nicholashusin, @golang/release.dmitshur commented on golang.org/x/build/cmd/relui: add metadata-based security comm fetching for RC releases10h
Thanks.dmitshur opened a change golang.org/x/build/cmd/relui: add metadata-based security comm fetching for RC releases11h
This has been working well for the "two minor releases" relui workflow.
Continue by making it available in "next RC" relui workflow next.
For golang/go#79037.dmitshur fixed an issue internal/sync: TestConcurrentCache failures11h
dmitshur fixed an issue internal/sync: TestConcurrentCache failures11h
I understand this should be fixed by https://go.dev/cl/794120 and https://go.dev/cl/794121 (CC @prattmic), closing. [internal/sync.TestConcurrentCache on gotip-linux-amd64-noopt](https://ci.chromium.…dmitshur commented on internal/sync: TestConcurrentCache failures11h
I understand this should be fixed by https://go.dev/cl/794120 and https://go.dev/cl/794121 (CC @prattmic), closing. [internal/sync.TestConcurrentCache on gotip-linux-amd64-noopt](https://ci.chromium.…dmitshur commented on github.com/go-gl/glfw/v3.3/glfw: Warnings when building using -tags wayland13h
We'll be able to pull it in once there's a stable GLFW release that includes that change. PR glfw/glfw#2833 is added to 3.5 milestone, so I understand it will be released in in a future GLFW 3.5 rele…dmitshur reviewed +2 on runtime: [release-branch.go1.26] tolerate vendor suffixes in Linux kernel release strings15h
dmitshur reviewed +2 on golang.org/x/build/devapp/owners: remove Rob Pike from various packages16h
Thanks.
cmd/doc was deleted in CL 689835 ('go doc' continues to handle its functionality), so this entire entry can also be removed.This Week
dmitshur reviewed +2 on golang.org/x/pkgsite/deploy: update Cloud Build Go version to 1.27rc11d
Thanks.dmitshur commented on golang.org/x/sys/cpu: handle vendor suffixes in parseRelease1d
(1 comment)
Thanks.dmitshur commented on golang.org/x/sys/cpu: handle vendor suffixes in parseRelease1d
(1 comment)
Is it applied in patch set 4? The change doesn't seem to be uploaded yet.dmitshur reviewed +2 on golang.org/x/website/_content/doc/go1.27: fix typo2d
Thanks.dmitshur merged a change github.com/go-gl/glfw/v3.4/glfw: gofmt not_wayland.go2d
Last Week
dmitshur opened a change github.com/go-gl/glfw/v3.4/glfw: gofmt not_wayland.go3d
For #419.
(CC @oliverbestmann.)dmitshur created branch in github.com/go-gl/glfw3d
gofmt-after-pr-420dmitshur fixed an issue github.com/go-gl/glfw: Linux, no buildtags on 3.4 does not expose `GetWaylandDisplay`.3d
I understand PR #420 fixed this, so closing.dmitshur commented on runtime: [release-branch.go1.26] tolerate vendor suffixes in Linux kernel release strings4d
(1 comment)
Yes, the other Gerrit footers are usually kept - this is covered at https://go.dev/wiki/MinorReleases#making-cherry-pick-cls:
> In the popup enter the branch name (like release-branch.g…dmitshur starred github.com/x448/float164d
dmitshur commented on cmd/gofmt: don't rewrite into smart quotes4d
A concern is that proposal conflicts (significantly overlaps) with an already-accepted but not yet implemented one at #54312. That proposal went through an analysis of the ecosystem as part of arrivi…dmitshur commented on golang.org/x/tools/go/types/internal/play: show Cursor path4d
(1 comment)
Noting here that it should also be possible to take advantage of this fmt printing behavior:
> 2. If an operand implements the [Formatter](https://pkg.go.dev/fmt#Formatter) interface, i…dmitshur commented on proposal: blanket approval for String and GoString methods4d
In the example provided, the phrasing "a fuller description of a Thing than [Thing.String]" seems more distinct than I'd expect from the description for the `GoString() string` method given at https:…dmitshur closed an issue net/http: add GODEBUG=httpmaxheadervalues=N [freeze exception]5d
dmitshur commented on golang.org/x/build/main.star: use lucicfg as a tool dependency6d
Thanks, using `go tool` for this is very interesting.
I'm a bit hesitant to actually switch to this because it would mean we deviate more from the approach that's supported by the LUCI team. It woul…dmitshur commented on runtime: handle nil pointer in sysFreeOS on sbrk platforms6d
The legacy trybots aren't supported anymore, so stopping this empty run. We'll remove the gerrit vote soon to avoid confusion. Currently supported trybots are triggered via the Commit-Queue+1 vote as…dmitshur reviewed +2 on golang.org/x/arch/...: disable Git line-ending conversion6d
A few notes Gerrit-related notes: @emmanuel@orijtech.com, please note that when starting trybots via the 'Choose Tryjobs' dialog, since this CL is inside the golang.org/x/arch repository, the builder…dmitshur commented on golang.org/x/build/internal/task: remove open CL checks to prevent waiting for empty CLs1w
(1 comment)
(Any leftover generated CLs can also be found and cleaned up via a query like https://go-review.googlesource.com/q/owner:gobot@golang.org+is:open.)dmitshur closed a change golang.org/x/arch/...: upgrade go directive to at least 1.25.0 [generated]1w
Replaced by CL 744640.dmitshur closed a change golang.org/x/playground/...: upgrade go directive to at least 1.25.0 [generated]1w
dmitshur closed a change golang.org/x/text/...: upgrade go directive to at least 1.25.0 [generated]1w
dmitshur closed a change golang.org/x/mod/...: upgrade go directive to at least 1.25.0 [generated]1w
dmitshur closed a change golang.org/x/debug/...: upgrade go directive to at least 1.25.0 [generated]1w
dmitshur closed a change golang.org/x/term/...: upgrade go directive to at least 1.25.0 [generated]1w
dmitshur reviewed +2 on golang.org/x/build/internal/task: remove open CL checks to prevent waiting for empty CLs1w
Thanks.
Noting that clTitle needed to be defined as a variable in part because it needed to be used in multiple places, including for the "past open CL" check. Now that it's only being used in the o…dmitshur reviewed +2 on golang.org/x/build/cmd/gomote: remove the gomote coordinator functionality1w
Thanks.dmitshur commented on go/ast: standardize deprecated comment tags1w
CC @griesemer, @golang/tools-team, @dominikh.dmitshur closed an issue runtime: concurrent struct access in grpc-go transport crashes only on AMD1w
dmitshur commented on golang.org/x/tools/go/ssa: remove incorrect hasTypeParams check1w
(1 comment)
These two lines seem to be missing a verb in front. 'Fixes' for both?dmitshur reviewed +2 on golang.org/x/blog/...: remove 2 hidden files, leave just README1w
dmitshur reviewed +2 on golang.org/x/blog/...: remove 2 hidden files, leave just README1w
This change is ready for review.dmitshur opened a change golang.org/x/blog/...: remove 2 hidden files, leave just README1w
These were missed in CL 324270. These files aren't needed,
and can be safely removed. This way they won't become out
of date, and they won't invite maintenance.dmitshur reviewed +2 on golang.org/x/arch/...: disable Git line-ending conversion1w
(1 comment)
If I understand correctly, this is an intentionally shortened version of a similar explanatory comment used in other repos:
https://cs.opensource.google/search?q=file:.gitattributes&sq=…dmitshur fixed an issue access: join golang/riscv64 maintainer team1w
Thanks. Added @HeliC829 to https://github.com/orgs/golang/teams/riscv64/members.dmitshur commented on golang.org/x/sys/windows: reject overlong inputs in NewNTString1w
CC @golang/windows.dmitshur commented on cmd/compile: internal compiler error invalid heap allocated var without Heapaddr1w
CC @golang/compiler.dmitshur commented on cmd/compile: reduce allocations by reusing SSA scratch state1w
CC @golang/compiler.dmitshur commented on golang.org/x/arch/x86/x86avxgen: TestOutput failure1w
CC @cherrymui, @golang/windows.dmitshur commented on golang.org/x/pkgsite: improve openapi.yaml1w
CC @golang/pkgsite.dmitshur commented on golang.org/x/image/bmp: add 1, 2 and 4 bits-per-pixel palette encoding support1w
CC @nigeltao, @robpike.Earlier
dmitshur commented on net/http/internal/http2: remove "Host" header from Request.Header1w
@kidnamedcudilovedrake-dot You've been posting on many issues recently. The issue tracker is used for discussing the issue, code changes are better handled as part of CLs (which is where a [CLA](http…dmitshur commented on golang.org/x/crypto/ssh: RSA parameter moduli maximum should be increased1w
CC @drakkan, @golang/security.dmitshur commented on golang.org/x/build/cmd/relnote: improve experience for documenting new standard library packages1w
Thanks, feel free to send a CL. See https://go.dev/doc/contribute.dmitshur opened an issue cmd/compile: cmd/compile/internal/gc fails to build (as part of running tests) under GOEXPERIMENT=newinliner1w
As of [CL 792120](https://go.dev/cl/792120), the gotip-linux-amd64-newinliner builder which tests with `GOEXPERIMENT=newinliner` fails to build cmd/compile/internal/gc:
```
FAIL cmd/compile [build f…dmitshur opened an issue github.com/actions/setup-go: Support release candidate alias ("nextstable"?) as a moving target1w
**Description:**
Currently setup-go supports "stable" and "oldstable" aliases. They are moving targets, so they make it convenient for repositories to target those versions, without needing to edit a…dmitshur commented on golang.org/x/exp/cmd/apidiff: non-deterministic output for "no longer implements"1w
CC @jba, @adonovan.dmitshur commented on github.com/go-openapi/testify/v2: didPanic relies on "panic called with nil argument" Error string equality, changes behavior in Go 1.271w
Thanks very much for resolving this!dmitshur commented on golang.org/x/vuln/cmd/govulncheck: govulncheck v1.4.0 runs into a Panic during scan1w
Thanks for confirming @noahbjohnson. That suggests govulncheck owners may consider temporarily working around by using an older x/tools while #80055 is investigated and resolved.dmitshur commented on golang.org/x/arch/loong64/loong64asm: TestObjdumpLoong64TestDecodeGoSyntaxdata failures1w
CC @golang/loong64.dmitshur commented on cmd/go: support quotes in `GOENV` file1w
CC @golang/command-line.dmitshur commented on golang.org/x/vuln/cmd/govulncheck: govulncheck v1.4.0 runs into a Panic during scan1w
If someone who's able to reproduce this wants to try building govulncheck from source, modifying it with `go get golang.org/x/tools@v0.44.0` (plus v0.45.0 is worth trying too), please see whether tha…dmitshur commented on golang.org/x/tools/go/ssa: RuntimeTypes panics on a parameterized type boxed in a generic method's closure1w
Thanks for reporting and bisecting this.
CC @golang/tools-team, @mrkfrmn, @griesemer.dmitshur commented on cmd/compile: inconsistent errors for init expr mismatches for vars and consts1w
CC @golang/compiler.dmitshur commented on golang.org/x/vuln/cmd/govulncheck: govulncheck v1.4.0 runs into a Panic during scan1w
Thanks for reporting.
CC @golang/vulndb.dmitshur opened an issue github.com/go-openapi/testify/v2: didPanic relies on "panic called with nil argument" Error string equality, changes behavior in Go 1.271w
**Describe the bug**
The `didPanic` function in `internal/assertions/panic.go` seems to try to detect instances of [`*runtime.PanicNilError`](https://pkg.go.dev/runtime#PanicNilError) error by checki…dmitshur commented on runtime: possible bug in moveSliceNoCap [1.26 backport]1w
@abtuteja Go minor releases are scheduled monthly, near the beginning of each month. So early July. See https://go.dev/wiki/MinorReleases.dmitshur commented on runtime: version parsing fails1w
Ping @bradfitz.dmitshur commented on golang.org/x/tools/go/analysis/passes: analyzer for removing canonical import comments1w
There's precedent for something along these lines in the "plusbuild" analyzer.
Do you suggest this analyzer should remove import comments only when the import math matches the actual import path of …dmitshur commented on golang.org/x/tools/go/analysis/passes: analyzer for removing canonical import comments1w
CC @adonovan, @matloob, @madelinekalil.dmitshur closed an issue build: build failure on go1.26-linux-amd64-misccompile1w
The LUCI infrastructure ran into a "i/o timeout" while invoking its own APIs. Nothing for Go to do here.dmitshur commented on golang.org/x/pkgsite: transient 500 errors on frontend during DB replica maintenance1w
CC @golang/pkgsite.dmitshur opened an issue cmd/compile: 2.29% regression in Dgeev/Circulant10-16 sec/op on linux/arm64 at 0252b4b1w
Discovered a regression in sec/op of 2.29% for benchmark Dgeev/Circulant10-16.
https://perf.golang.org/dashboard/?benchmark=Dgeev/Circulant10-16&platform=linux/arm64&repository=go&branch=master
http…dmitshur opened an issue cmd/compile: 5.10% regression in RepeatNew-88 sec/op on linux/amd64 at c59ae5c1w
Discovered a regression in sec/op of 5.10% for benchmark RepeatNew-88. Not quite clear which commit.
https://perf.golang.org/dashboard/?benchmark=RepeatNew-88&platform=linux/amd64&repository=go&bran…dmitshur commented on os/signal: TestCtrlBreak failures1w
From a triage meeting, @prattmic points out this test has a time.Sleep(1 * time.Second) so this might be a flake due to the subprocess not starting in that constant time.dmitshur commented on cmd/cgo/internal/test:external-g0: Test9400 failures1w
CC @golang/compiler.dmitshur commented on cmd/go: spurious leading blank line before `ok` when a passing test writes unterminated output1w
Thanks for the report. Would you like to send a CL? https://go.dev/doc/contributedmitshur commented on cmd/cgo/internal/test:external-g0: unrecognized failures1w
CC @golang/compiler.dmitshur commented on cmd/cgo/internal/test:auto-pie: Test9400 failures1w
CC @golang/compiler.dmitshur commented on runtime: concurrent map read and map write with sync.RWMutex on ppc64le [1.26 backport]1w
Thanks for making this backport request @Jorropo. It's approved now. Since you're the author of the fix CL, if you don't mind, please create backport CLs for this and #79878 following https://go.dev/…dmitshur fixed an issue all: switch to Go 1.27 as default inside Google1w
In a release meeting, we reviewed this blocker for the public Go 1.27 RC 1 and consider it complete. Closing.dmitshur commented on os/signal: TestCtrlBreak failures1w
CC @golang/runtime, @golang/windows.dmitshur commented on golang.org/x/build/internal/task: TestFindGoogleGroupsThread/[security]_golang.org/x/crypto_fix_pre-announcement failures1w
This test reaches out over the internet to a service (Google Groups), runs a search query and checks that the algorithm still works as expected. Every so often it seems the response doesn't include t…dmitshur reopened an issue cmd/fix: reflecttypefor replaced TypeOf(f) with TypeFor[func(...)](), losing relationship with symbol f1w
This is a cmd/fix issue in Go1.27 milestone, but so far it was closed by a CL in the x/tools repo. Reopening to make sure this change makes its way into cmd/fix in time for Go 1.27.0. This still need…dmitshur commented on golang.org/x/build: update gopls version requirements as part of the Go toolchain release workflow2w
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. …dmitshur commented on golang.org/x/build: automate maintenance of pinned Go toolchain/runtime versions in Dockerfile and app.yaml files2w
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:…dmitshur commented on crypto/tls: only set LocalCertificate when a certificate is presented2w
@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…dmitshur commented on golang.org/x/tools/go/packages: TestAdHocOverlays/GO111MODULE=auto failures2w
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…dmitshur commented on crypto/mldsa: Verify accepts uninitialized PublicKey with empty signature2w
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.dmitshur commented on crypto/tls: provide a way to access local certificate used to set up a connection [freeze exception]2w
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…dmitshur commented on crypto/tls: LocalCertificate is populated on resumed TLS <=1.2 server connections2w
CC @rolandshoemaker, @golang/security.dmitshur commented on crypto/tls: TLS 1.3 post-handshake alerts not surfaced to the client2w
CC @golang/security.dmitshur commented on cmd/gofmt: comment alignment chunking behaviour different on MacOS vs Linux2w
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…dmitshur commented on time: TestAfterQueuing/impl=func failures2w
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…dmitshur commented on os: TestRootConsistencyStat/Lstat failures on XFS due to size of directories not being the same2w
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.dmitshur pushed to
main in dmitri.shuralyov.com/service/change1ydmitshur commented on dmitri.shuralyov.com/blog: Trying out the Oculus Rift CV1 for the first time2y
July 4, 2024. Today I got a chance to try out the Apple Vision Pro. :)dmitshur pushed to
main in dmitri.shuralyov.com/scratch2y