Activity
Yesterday
dmitshur commented on runtime: implement stackcheck for arm6421h
(I meant to say macOS 26; here: https://ci.chromium.org/b/8682262972831779137.)dmitshur commented on runtime: implement stackcheck for arm6421h
The darwin trybot with macOS 16 seemed to stall, is that unrelated? I started it again to get more data points.dmitshur commented on doc: document new ppc64/linux features22h
The net/http:nethttpomithttp2 failure may be issue #79387 or related. Not caused by this change, so bypassing.dmitshur commented on net/http: deflake HTTP/3 tests22h
[CL 777921](https://go.dev/cl/777921) added a test skip for now, so removing release-blocker label (for Go 1.27) and moving to early-in-cycle Go 1.28.dmitshur commented on golang.org/x/text/unicode/bidi: DefaultDirection(LeftToRight) is silently ignored23h
@qsq8t65pxs It's important for backport requests to include a rationale - please see https://go.dev/wiki/MinorReleases. This issue is about a package in x/text; is there involvement of the standard l…dmitshur reviewed +2 on doc: document new ppc64/linux features1d
dmitshur commented on golang.org/x/crypto: tag v1.0.01d
I agree that x/crypto behaves as if it’s already tagged v1.0.0, both when this was filed and now, it just hasn’t been tagged v1 yet, and it should. This issue hasn’t been progressing as is, and…dmitshur commented on cmd/api: run api check on all golang.org/x modules that have reached v1.0.0 or higher1d
Yes, that’s true. They should probably be tagged v1, their owners just haven’t done it yet. See issue #56325 (CC @FiloSottile) for example. We can still include them in scope of this issue.
I ti…dmitshur commented on golang.org/x/build: widespread builder unavailability, including linux/amd64, on 2026-05-141d
I intended to leave it pinned for some time after closing in case people whose CLs ran into this tried to look here. It’s probably fine to unpin by now. Thanks.This Week
dmitshur reviewed +2 on doc: document new ppc64/linux features1d
Thanks.
```suggestion
### Linux {#linux}
```
Also, if there was a tracking issue, it'd be helpful to mention it here in an HTML comment (similar to line 5 above). If not, then nothing to do.
```s…dmitshur reviewed +2 on net/http: disable HTTP/3 tests prior to freeze1d
Thanks.
The "task did not start, no resource" infrastructure failures were due to issue #79410, which is resolved, so starting trybots again.dmitshur commented on golang.org/x/mobile/bind: align Objective-C setter selectors with sanitized property names1d
The "task did not start, no resource" infrastructure failures were due to issue #79410, which is resolved, so starting trybots again.dmitshur fixed an issue golang.org/x/build: widespread builder unavailability, including linux/amd64, on 2026-05-141d
dmitshur fixed an issue golang.org/x/build: widespread builder unavailability, including linux/amd641d
dmitshur commented on golang.org/x/build: widespread builder unavailability, including linux/amd641d
It's still working; "Bots: 102" as if this posting. Closing this as resolved, and I'll follow up in other issues on what's left to do.dmitshur commented on golang.org/x/build: widespread builder unavailability, including linux/amd641d
It seems to be helping so far, linux/amd64 builders are showing up:
<img width="478" height="393" alt="Image" src="https://github.com/user-attachments/assets/062662f0-cfab-4270-a045-c9f22b523b78" />…dmitshur commented on golang.org/x/build: widespread builder unavailability, including linux/amd641d
A likely cause is found, trying a fix.dmitshur commented on golang.org/x/build: widespread builder unavailability, including linux/amd641d
Those Debian 13 builder machines above are for the linux-amd64_debiansid builder and may be unrelated.dmitshur commented on golang.org/x/build: widespread builder unavailability, including linux/amd641d
The linux/amd64 builder query at https://chromium-swarm.appspot.com/botlist?f=cipd_platform%3Alinux-amd64&f=machine_type%3An1-standard-16&f=os%3ADebian-11&f=pool%3Aluci.golang.try-workers finds 0 bot…dmitshur commented on all: the tree is horribly flaky1d
@nicholashusin Thanks, that seems like a separate builder infrastructure problem. I filed #79410 for it.dmitshur opened an issue golang.org/x/build: widespread builder unavailability, including linux/amd641d
We're aware of an issue where many of the builders involved in the default trybot set are unavailable. For example, as visible at https://ci.chromium.org/ui/p/golang/builders/try-workers/gotip-linux-…dmitshur commented on all: the tree is horribly flaky2d
TestTransportBodyReadError and other net/http flakes are likely related to the known flakes tracked in issue #78737 (CC @neild, @nicholashusin). There have been recent changes that helped, like https…dmitshur fixed an issue net/http:nethttpomithttp2: TestTransportClosesBodyOnError/h3 failures2d
Closed by [CL 777740](https://go.dev/cl/777740) (commit c22f92a751ed649cd5face58a576d0b13e3d6db7).dmitshur commented on net/http:nethttpomithttp2: TestTransportClosesBodyOnError/h3 failures2d
Closed by [CL 777740](https://go.dev/cl/777740) (commit c22f92a751ed649cd5face58a576d0b13e3d6db7).dmitshur commented on golang.org/x/sys/unix: merge Linux readv/writev implementation with Darwin/OpenBSD2d
(1 comment)
The symbol name and doc comment are slightly different (d vs D). Maybe the doc comment name better and it's worth renaming this unexported function, but in general they should match one …dmitshur reviewed +1 on net/http: fix hang in TestTransportClosesBodyOnError/h32d
Thanks! Leaving to Damien.dmitshur commented on net/http:nethttpomithttp2: TestTransportClosesBodyOnError/h3 failures2d
CC @nicholashusin.dmitshur commented on golang.org/x/crypto/ssh: return partial success immediately from publickey auth3d
The trybot failure on that one builder seems like an infrastructure problem; sent crrev.com/c/7842813 (CC @cherryyz@google.com) to start annotating such cases accordingly in the future. Retrying tryb…dmitshur commented on debug/pe: missing saferio validation in ZLIB section decompression3d
CC @golang/windows.dmitshur commented on cmd/go/internal/telemetrystats: add go/platform/target/port:*-* counter3d
Thanks.dmitshur commented on cmd/fix: x/tools/go/analysis/passes/modernize: slicescontains hoists needle expression, changing side effect count4d
One way to keep the function (with possible side effects) executed the same number of times might be to use slices.ContainsFunc with a trivial equality func. That is, if the for range loop is rewritt…dmitshur commented on cmd/fix: x/tools/go/analysis/passes/modernize: slicescontains hoists needle expression, changing side effect count4d
@gopherbot Please consider this for backport to Go 1.26. It's needed to prevent `go fix` from incorrectly rewriting code to use `slices.Contains` in some cases when doing so could cause an unintended…dmitshur commented on golang.org/x/crypto/blake2b: merge go125.go into blake2b_test.go5d
Thanks.Last Week
dmitshur reopened an issue runtime: crash in WASM plugins without open file descriptors due to `poll_oneoff` call1w
Reopening since the information in https://github.com/golang/go/issues/78513#issuecomment-4215930937 suggests this can be an enhancement.dmitshur reopened an issue runtime: crash in WASM plugins without open file descriptors due to `poll_oneoff` call1w
Reopening since the information in https://github.com/golang/go/issues/78513#issuecomment-4215930937 suggests this can be an enhancement.dmitshur commented on golang.org/x/benchmarks/go.mod: update golang.org/x dependencies1w
Done in PS 3 by updating to `x/net@v0.54.1-0.20260508232935-23ee2efe81a3`.dmitshur commented on golang.org/x/build/go.mod: update golang.org/x dependencies1w
(1 comment)
I'll update this to v0.54.1-0.20260508232935-23ee2efe81a3 to pull in the fix in CL 776180, needed to break build errors at tip.dmitshur reviewed +2 on golang.org/x/net/http2: avoid API changes when built with go1.271w
Thanks.
(nit) Could get rid of ": removed" here, it's not needed.
Edit: Already resolved in PS 5.
(Same here and the two lines below.)
Edit: Already resolved in PS 5.
We don't want to check in t…dmitshur commented on golang.org/x/benchmarks/go.mod: update golang.org/x dependencies1w
The change itself is good, though trybots are reporting a build breakage at tip because x/net v0.54.0 accidentally included breaking API changes (that affect tip only, not any of the stable Go releas…dmitshur reviewed +2 on golang.org/x/net/http2: avoid API changes when built with go1.271w
Thanks.
There are a few more symbols that also need attention, in case you prefer to handle them in the same CL, though of course it's fine to submit this one as is since it's making forward progres…dmitshur opened an issue cmd/api: run api check on all golang.org/x modules that have reached v1.0.0 or higher1w
The cmd/api check runs in the main Go repo and is generally very helpful there. There are some opportunities to extend it, such as issues #53205 and #56773. I didn't find an existing issue for extend…dmitshur closed an issue cmd/api:check: TestCheck failures1w
Looks like a memory bit flip on a darwin builder that happened exactly once in years. Closing in favor of issue #77515.dmitshur commented on golang.org/x/tools/go.mod: update golang.org/x dependencies1w
(1 comment)
I'm not sure off hand, other than it's plausibly related to https://go.dev/ref/mod#graph-pruning, but a few observations:
1. these records are only for go.mod files of x/crypto modules,…dmitshur commented on golang.org/x/telemetry/x/telemetry/config: add counter for goimports invocation1w
(3 comments)
```suggestion
internal/chartconfig: add counter for goimports invocation
```
(The "x/telemetry" prefix is needed on the issue tracker because it tracks all x/ repos in one place, where…dmitshur fixed an issue golang.org/x/tools/cmd/goimports: add counter for each invocation1w
dmitshur fixed an issue golang.org/x/tools/cmd/goimports: add counter for each invocation1w
Issue #75651 also exists to track adding the telemetry config. So this can proably stay focused on adding the local counter, which was done in [CL 700595](https://go.dev/cl/700595). Closing again.dmitshur commented on golang.org/x/tools/cmd/goimports: add counter for each invocation1w
Issue #75651 also exists to track adding the telemetry config. So this can proably stay focused on adding the local counter, which was done in [CL 700595](https://go.dev/cl/700595). Closing again.dmitshur fixed an issue golang.org/x/telemetry/config: add counter for toolchain VCS usage1w
Thanks for the suggestion to check local counters in `go env GOTELEMETRYDIR`. They seem as expected to me, and "go/vcs" shows up at https://telemetry.go.dev/config now (thanks to [CL 775820](https://…dmitshur commented on cmd/go/internal/telemetrystats: drop go/platform/target/{goos,goarch}:*1w
(1 comment)
This change is ready for review.
Hold submission for a later release, though it's fine to review now.dmitshur commented on cmd/go/internal/telemetrystats: add go/platform/target/port:*-* counter1w
This change is ready for review.dmitshur reviewed +2 on golang.org/x/build/main.star: add configs for sizespecializedmalloc perf_vs_parent builders1w
Thanks. I wasn't very familiar with our perf_vs_parent runmod, but good to learn more about it.
Just noting that I expect (but haven't confirmed) that it will have the GOEXPERIMENT env var set both …dmitshur commented on golang.org/x/build/cmd/gorebuild: log at start of GerritTarGz1w
Thanks.dmitshur opened a change cmd/go/internal/telemetrystats: drop go/platform/target/{goos,goarch}:*1w
They provide a subset of the information that the newer port:*-* counter
provides, making them generally redundant. They were never uploaded, and
there are no plans to start using them, so remove the…dmitshur commented on golang.org/x/telemetry/internal/chartconfig: add go/platform/target/port:*-* counter1w
(1 comment)
Using two brackets for expansions isn't supported. Even if it were supported, we probably don't want to permit unexpected combinations (like aix-386) to be accepted for upload, so I'll c…dmitshur opened a change golang.org/x/telemetry/internal/chartconfig: add go/platform/target/port:*-* counter1w
The accepted GOOS and GOARCH values come from the 49 ports that
includes 2 broken ports (they may still be attempted to be used)
as reported by 'go tool dist list -broken' at tip, Go 1.27 to be.
For…dmitshur opened a change cmd/go/internal/telemetrystats: add go/platform/target/port:*-* counter1w
CL 587115 added separate counters for target GOOS and target GOARCH:
go/platform/target/{goos,goarch}:*
For the purpose of being able to tell usage of each target port
(telemetry proposal go.dev/i…dmitshur closed a change golang.org/x/open2opaque/...: update golang.org/x dependencies1w
This change has been applied as https://go.googlesource.com/open2opaque/+/3d04330bec09d438a41877cf8c354f63a5fab476.dmitshur commented on golang.org/x/crypto/x509roots/fallback/bundle: fix bundle test with Go 1.27+1w
(1 comment)
Since those steps are fairly predictable and might be easier to do now while the context is fresh in memory, prepared CL 775782 and CL 775783 for that in case it helps.dmitshur opened a change golang.org/x/crypto/blake2b: merge go125.go into blake2b_test.go1w
The go1.25 build constraint is guaranteed to always be satisfied because
the go directive is at 1.25.0, so the separated out go125.go file is not
needed. Move the assertion that the *xof type impleme…dmitshur opened a change golang.org/x/crypto/x509roots/fallback/bundle: make subjectsEqual stricter on Go 1.27+1w
This gradual step towards removing/inlining subjectsEqual can happen
after Go 1.27.0 is released and the bundle starts being generated
with it.dmitshur opened a change golang.org/x/crypto/x509roots/fallback/bundle: inline subjectsEqual1w
This final step of removing/inlining subjectsEqual can happen after
Go 1.28.0 is released.dmitshur commented on cmd/go: add -buildversion build flag1w
@thepudds Thanks for mentioning the VERSION files used by the Go toolchain; I was going to do that too since it hadn't come up yet, and it seems good to at minimum consider in this proposal. I'll not…dmitshur reviewed +2 on golang.org/x/telemetry/godev: update telemetry docker versions to 1.251w
Thanks.
```suggestion
With the go.mod go version updates, we need at least Go 1.25 to build
```
Using 1.25 is certainly fine as is, since it meets the minimum requirement of this module. Just notin…dmitshur commented on golang.org/x/build/cmd/gorebuild: log at start of GerritTarGz1w
Friendly ping since it's been a while. Thanks.dmitshur opened a change all: [release-branch.go1.4] update to be compatible with C231w
The 'typedef int bool;' line has become a compile error as of -std=c23
because bool became a reserved keyword. true and iszero are also newly
reserved.
Gain compatibility with C23 by switching to '#…dmitshur reviewed +2 on go/importer: un-deprecate importer.ForCompiler1w
Thanks.dmitshur commented on golang.org/x/build/internal/relui: return an authenticated-only Gitiles URL in ArchiveURL1w
Thanks.dmitshur reviewed +2 on golang.org/x/tools/gopls/internal/analysis/errorsastype: imporove example clarity1w
Thanks.dmitshur commented on golang.org/x/tools/gopls: add errorsastype analyzer1w
@mpoliwczak34@gmail.com Thanks for making this change. I left a small comment inline.
A comment/suggestion on the example, which is used in multiple places.
I recognize that it's intended to show a…dmitshur opened a change golang.org/x/build/internal/relui: return an authenticated-only Gitiles URL in ArchiveURL1w
We're intending to always use authentication here, so the /a/ endpoint
should work. (It would tell us if somehow we're making unauthenticated
requests, and maybe has different quotas associated with …dmitshur commented on cmd/go: add `-test` to `go doc`1w
https://go.dev/doc/comment documents the concept of "Go doc comments" and how to write them. Go users who are looking to document exported APIs rely on the mechanisms there because it has effect on t…dmitshur reviewed +2 on golang.org/x/build/repos: add dot-github to mirror to golang/.github1w
Thanks.
Feel free to submit as soon as as https://go.googlesource.com/dot-github exists. (Submitting it before then would cause x/build/cmd/gitmirror to run into errors if we were to redeploy it, so…dmitshur commented on golang.org/x/open2opaque/...: update golang.org/x dependencies1w
(1 comment)
I almost forgot and somehow remembered this, [again](https://go-review.googlesource.com/c/open2opaque/+/678895/comment/0188ea8c_6055f78a/). This time before this CL is submitted, so Hold…dmitshur opened an issue google.golang.org/open2opaque: Go tip (Go 1.27 to be) runs into "export data version 3 is greater than maximum supported version 2" problem because required x/tools version isn't new enough for Go 1.27 needs1w
As visible on the post-submit dashboard at https://ci.chromium.org/p/golang/g/z-open2opaque-gotip-by-go/console, there are on the order of 400 failing tests at Go tip (Go 1.27 to be), for example:
`…dmitshur opened an issue golang.org/x/build/cmd/golangbuild: add support for test artifacts in LUCI1w
Proposal #71287 to add support for test artifacts was accepted and implemented in Go 1.26. We should update golangbuild accordingly, so that it's possible for us to take advantage of this new feature…> I'm happy to make whatever changes are needed to packages.Load but I'm not sure what they are.
@adonovan The documentation at https://pkg.go.dev/golang.org/x/tools/go/packages#Config.Env includes …dmitshur commented on golang.org/x/telemetry/config: add counter for toolchain VCS usage1w
@h9jiang Given [CL 729480](https://go.dev/cl/729480) is submitted, do you know if it's expected to start to show up at https://telemetry.go.dev/config now? Is it waiting on a redeploy to pick that ch…dmitshur commented on runtime: TestFinalizerOrCleanupDeadlock/Finalizer/Panic failures1w
CC @golang/compiler.dmitshur commented on cmd/compile: known bits and prove constant folding can impede memcombine1w
From triage, this sounds like an enhancement. @Jorropo Are you planning to work on this or did you mean to report it so someone else can pick this up?From triage, we discussed this and believe the go command itself is working as intended. It's expected that the intended version of the go command needs to be first in PATH environment variable. We'r…dmitshur closed an issue runtime:mayMoreStackPreempt: TestNotInGoMetric/CgoCall failures1w
dmitshur commented on runtime: TestBigStackCallbackCgo failures1w
From triage, it seems windows-386 is running into 180 second timeout in some packages like runtime, net/http more frequently recently.dmitshur commented on cmd/asm: don't allow writes outside of a function's stack frame1w
CC @golang/compiler.
From triage, we think this probably cannot be made to fail to compile, but instead can be a vet check.dmitshur commented on go/importer: documentation of lookup parameter of ForCompiler can be clarified1w
The cmd/api checker bug is fixed, and there's no API change involved, so I think this can become a regular issue to improve documentation clarity. Retitled.dmitshur closed an issue crypto/internal/fips140/drbg: backport CL 774221 to Go 1.26 [1.27 backport]1w
This is a false positive due to #27489: the backport request was for 1.26 only, "1.27" happened to be mentioned for an unrelated reason (CC @cherrymui). Though it means the heuristic of ignoring othe…dmitshur commented on golang.org/x/telemetry/config: add counter for toolchain VCS usage1w
go/vcs:{git,hg,svn,bzr,fossil} covers all of the VCSes but one: the "mod" pseudo-vcs which represents the "neither Git, Mercurial, etc. was used" case. Given the goal of this proposal is to give insi…dmitshur commented on : setup `.github` repo for default community health files1w
I think it's a good idea at least for the PULL_REQUEST_TEMPLATE file. That template seems pretty general and applies to all Gerrit repositories mirrored to GitHub that accept PRs via [gerritbot](http…dmitshur commented on golang.org/x/telemetry/config: counters for target GOOS/GOARCH1w
I'm supportive of adding these counters.
Some of the Go ports may be commonly targeted via cross-compilation from other host platforms, and some Go ports are only accessible as cross-compilation tar…dmitshur opened an issue cmd/dist: inverted precedence for && and || in exprParser1w
cmd/dist has a small //go:build constraint parser and evaluator for the needs of bootstrapping. Back when it was added ([CL 359314](https://go.dev/cl/359314), CC @rsc), go/build/constraint couldn't b…Earlier
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 time1y
July 4, 2024. Today I got a chance to try out the Apple Vision Pro. :)dmitshur pushed to
main in dmitri.shuralyov.com/scratch2ydmitshur created package in dmitri.shuralyov.com/scratch/quine2y
dmitshur merged a change dmitri.shuralyov.com/scratch: quine: add package quine2y
dmitshur reviewed +2 on dmitri.shuralyov.com/scratch: quine: add package quine2y
LGTM. Thanks, and congrats on your first new Go package here!
Done in PS 2.
Patch set 2 seems to resolve this.dmitshur merged a change dmitri.shuralyov.com/scratch: add AUTHORS.md file2y
dmitshur reviewed +2 on dmitri.shuralyov.com/scratch: add AUTHORS.md file2y
Thanks! If it's ready to be submitted from your side, I can do that now.dmitshur pushed to
main in dmitri.shuralyov.com/html/belt2ydmitshur commented on dmitri.shuralyov.com/scratch: main: add package quine2y
They are. Although Go can make them too easy via `go:embed`.
See some initial comments.
I suggest either adding a quite that can be licensed via the existing BSD-3-Clause LICENSE at the top level o…