Activity

Today
Thanks for preparing this change. As noted in the [README](https://go.googlesource.com/vgo#obsolete), this repository is an archive, preserved for historical interest only. It's not actively used nor…
Thanks. I see a lot of uses of DeploymentMap in this CL, but I'm having a hard time finding any one place that gives it a clear description. Given it's a map of A to B, what do A and B represent? I …
Yesterday
Thanks. Noting that this whole "Confirm PRIVATE-track security CLs" step was meant to be temporarily guard against human release coordinators accidentally pasting in the wrong ref until the metadata…
Yep, relui parameter definitions are basically free so it's good to specialize them to be more precise when applicable (such as here). Thanks.
Thanks. This is a general comment. I see a pattern across various CLs to convert some method-based tasks into function-based tasks and provide dependencies to them as parameters (wf.Const since they…
I wished (for purposes of readability of the CL stack) this was a part of CL 826666 rather than happening later, but maybe these couldn't be moved earlier until some of the refactors in between. Tha…
This is a bit unfortunate because it sets a slightly confusing precedent, and one would expect this to be something that's easier to do programmatically than to expect humans to do it. But I think it…
Thanks. The '%' is needed before the first [push option](https://gerrit-review.googlesource.com/Documentation/user-upload.html#push_options), and ',' separates multiple options. So I think as writte…
Thanks. I think fairly modern versions of `git` support fetching a revision directly via a `--revision` flag, so it might be viable to completely remove the need for callers to specify a ref. But th…
Thanks. Please document that a nil `listener` means to use a basic verbose listener, so that callers don't need to read implementation details of this helper to be able to rely on it.
Very nice to see this. Thanks. (I guess we can't do this for any tests that depend on a real database dependency, but those are a small subset; most release-related tests just use the workflow packa…
Thanks. Note that the canonical source of this package is in x/website; this is an x/build copy. The API change below is fine to make, but please also send it to x/website to keep them in sync and …
Thanks. While looking at this line (that this CL happens to touch), it's noticeable that this too can eventually be simplified by taking advantage of either `http.FileServerFS` or `http.Dir`. Pleas…
Thanks. We're deploying relui [with Go 1.27](https://cs.opensource.google/go/x/build/+/master:cmd/relui/Dockerfile;l=5;drc=de126992084793ed2efd31a4babdf01684b03c10), and if it's really worthwhile to…
Thanks. I'm not sure how easy it'll be for a person seeing this to tell what "handler" refers to. Maybe mention OnStall more explicitly.
This seems fine. I expect there will still be some instances where it's easier to create a dedicated testing helper, so not absolutely everything has to be de-duplicated and made general purpose, but…
Thanks. Nice to see this. As a side note, this is the first time I'm seeing the term "riders". The closest I knew of was git commit message footers/trailers, but I guess "riders" refer to the "Fixe…
Thanks. Should this return a non-nil error if the issue doesn't exist? Similarly to GetIssue above. ``` if !ok { return nil, fmt.Errorf("the issue %v does not exist", number) } ```
Thanks. It might help to note which type is the input to this template. For example, that'd make it easier to get to the definition of "{{.ID}}" and look up its [meaning](https://pkg.go.dev/golang.o…
Thanks. Is it viable (and helpful) to have CheckSecurityIssues also check that when rm is nil, there are exactly 0 security issues?
Thanks. Note that it can generally be useful to document fields for templates, and maybe include example values. Compare with above and below. Not having any docs means that readers can only derive…
This Week
This bug doesn't exist in Go 1.26. This backport issue was opened only because "1.26" was mentioned; closing.
This bug doesn't exist in Go 1.26. This backport issue was opened only because "1.26" was mentioned; closing.
(4 comments) For golang/go#nnn? It'd be good to have some issue to track the state of this experimental builder. See my other inline comment; just pointing out here that this is where you can see t…
Last Week
Thanks. https://go.dev/blog/go1.13-errors#whether-to-wrap suggests: > Wrap an error to expose it to callers. Do not wrap an error when doing so would expose implementation details. If it's not nec…
@filippo@golang.org Note that 5 crypto/rand:gofips140 tests without -short flag [seem to fail](https://ci.chromium.org/b/8669790779333004049/test-results) as of this CL.
This reverts CL 834945 (commit 936cd9c3e8585b3bb1ef0ba83488bfe78c9bf61c). Reason for revert: Breaks TestAllDependencies test on longtest builders. That test will also need to be updated to not write…
Issue #68790 added functionality to watchflakes to watch and report broken bots. A known limitation is that it's willing to report a given unique builder at most once, but it neither reopens¹ a prev…
There was another instance of 20 consecutive failures (due to the make.bash problem between [CL 830064](https://go.dev/cl/830064) and [CL 831204](https://go.dev/cl/831204)) placing the bot into quara…
Thanks. Thanks for finding the context of where it was added. Since it has no current users, and the newer functionality seems to superseded it, I think this CL is a good prompt to eventually drop …
(1 comment) What do you think of naming this `mustHaveGofmt`, similarly to the pattern used in the [internal/testenv](https://go.dev/pkg/internal/testenv) package and [`mustHaveWorktree`](https://cs…
Earlier
This change is ready for review.
Set -o=/dev/null when building a test command so that GOROOT isn't written to. GOROOT may not be writable.
This change is ready for review.
Use a temporary directory instead. GOROOT may not be writable.
LUCI builder names encode the release branch in front, such as "gotip-linux-amd64" or "go1.27-linux-amd64".
Thanks. This looks good to me, but I'll give Jonathan a chance to also look.
(1 comment) Makes sense and sounds good, thanks!
Thanks. ```suggestion website/tour: display notfound.html on bad tour page (404) ``` It might be slightly easier to reason about the logic if this variable is always defined, and its value is set t…
@madelinekalil Does this bug apply to 1.26 and 1.27, or 1.27 only? Asking given our policy to support [both Go releases equally](https://go.dev/issue/34536#issuecomment-572188389).
Proposals are already supported, in the sense they're listed as issues at https://goissues.org/ with a "Proposal" label. See [prefixtitle.ParseIssue](https://pkg.go.dev/dmitri.shuralyov.com/go/prefi…
Yes, it it failed while fetching dependencies because a GET request to the module mirror returned 502 Bad Gateway.
Is https://github.com/shuijingwan/go-tour-i18n/issues the right issue tracker where reports related to the translated tours should be filed? If so, please update the "submit feedback" button in the t…
It may be helpful to hear back on the question above, but I'll note that testing standard library packages with GO111MODULE=off is documented as not something that's expected to work - see `go help …
### Go version go version go1.27.1 darwin/arm64 ### What did you do? Prior to filing this issue, I forgot that it was already decided and documented that testing the Go standard library with GO111…
When working with GCS, one can end up with folders that are either implicit (aka "simulated"?) or explicit (aka "zero-byte object whose name ends with a trailing / delimiter"). Currently the gcsfs.Ne…
In addition to the above, perhaps we could enable the race detector and see if that uncovers something we're not seeing locally? [CL 827824](https://go.dev/cl/827824).
dmitshur commented on access: qiulaidongfeng approvers3w
CC @golang/release.
Bisected the failure to [CL 814681](https://go.dev/cl/814681), which updated cloud.google.com/go/storage from v1.31.0 to v1.59.2. Bisected that further to v1.50.0 as the last version that works while…
On August 27, we noticed a case where `buildToOutputs` panicked during a relui workflow execution. The panic revealed a missing error check, which [CL 823324](https://go.dev/cl/823324) has since fixe…
During one of the workflow runs for Go minor releases on August 11, 2026, we ran into an unexplained relui behavior: > [...] something up with relui - some of its tasks have appeared to stall, not m…
dmitshur starred github.com/go-git/go-git/v64w
dmitshur pushed to main in dmitri.shuralyov.com/service/change1y
6140fdcb140798fe4fda313c57be133bf235e796maintner, gerritapi: handle draft status
ce8900dcd6898d396808d962fd777dcf7be445e9gerritapi: pass context to Gerrit calls
96ed021e15235cb4abcdaa86b88cc271e47f04c1add minimal go.mod
July 4, 2024. Today I got a chance to try out the Apple Vision Pro. :)
dmitshur pushed to main in dmitri.shuralyov.com/scratch2y
5eb48b5f5d31d39777719edb35d37b724f183dc8quine: add load-bearing trailing space
dmitshur created package in dmitri.shuralyov.com/scratch/quine2y
LGTM. Thanks, and congrats on your first new Go package here! Done in PS 2. Patch set 2 seems to resolve this.
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/belt2y
d8009a3578d1be4dafb93e9ee4894d2bbd2b5e3badd OnClick field to CommitID
63f3644d8635396fd13789affe363ee9f693e8ecadd dark mode support in Reference
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…
Thanks! Congrats on your first change. :D See one inline comment that's unresolved (yellow border). You can leave a draft comment like "Done." and mark the 'Resolved' checkbox, then when you upload …
dmitshur pushed to main in dmitri.shuralyov.com/go/generated3y
e1de015411532fa144166aada4201ee443800425add test case with no final newline
6904a2a3d88d6c3ad39737a7c5bf226f5ebbd482modernize test code slightly
dmitshur pushed to main in dmitri.shuralyov.com/gpu/mtl3y
85de2813cf6bd8d6d2f0240fdebf943cbffc2b8afix "supportsFamily not found" warning on macOS 10.13 and 10.14
dmitshur pushed to main in dmitri.shuralyov.com/gpu/mtl3y
b78c9fe623cca0431d866c9e206d3f83665bcf8bdeprecate FeatureSet and Device.SupportsFeatureSet
2a3c46a829b92964146abf7f6c2d649cd66cce97add GPUFamily and Device.SupportsFamily
I agree with the points made above. This entry tried to say "use this language feature when it's appropriate; don't use it when it's not", which can be said for any language feature. I'll close this …
dmitshur pushed to master in dmitri.shuralyov.com/service/change4y
67e22b2f18a260a33a98c6a7d601726a58c53767maintner: update for GitCommit API change
Go fuzzing support is out of beta and no longer uses this build constraint. It should be replaced with `go1.18` by now. Done in PS 3. I'm following the Go style for commit messages, which chooses…