Activity

Yesterday
Add the ability to have builds apply only to select Go versions according to a module-query-like but fictional syntax. We don't need to support all arbitrary queries right away, so start with a small…
The `cmd/release` command is currently configured to use the `freebsd-{amd64,386}-11_1` builders for the `freebsd` release targets. However, we've documented that Go 1.13 onwards requires at least…
The `freebsd-amd64-race` builder currently uses `host-freebsd-11_1-big`. Go 1.13 and newer require FreeBSD 11.2 or newer. We should update this builder accordingly. If our assumption is that newer…
At the start of each code freeze, we should evaluate the builders used to make the upcoming major Go release, and confirm they are the most appropriate choice out of what is available. The start o…
The current Go tag parser supports only final releases, not betas and not RCs. It would become more useful if it supported all release types. There are some places in x/build where we've wanted to us…
(1 comment) Maybe we can improve this panic text to make it easier to understand what should be done to fix the problem? Feel free to edit it if you think so.
(1 comment) An entry needs to be added to the internal/gophers package.
(3 comments) Please wrap this line to a more comfortable width, per https://golang.org/wiki/CommitMessage ("the text should be wrapped ..."). This is in scope of issue #18548 (also see #18917). We …
dmitshur pushed to master in github.com/shurcooL/home1d
91c5682bc2aa970ba2311282230a37f1b27e4c1csupport HEAD method in ?go-get=1 requests
DO NOT REVIEW / DO NOT SUBMIT: This is a draft CL that goes with https://golang.org/issue/40477#issuecomment-667809154.
> 1. Write a CL. Examples: https://golang.org/cl/245379, https://golang.org/cl/245380. If the site requires more than just adding a pattern, describe your changes here first. I tried to create a C…
This Week
dmitshur pushed to master in github.com/shurcooL/githubv41d
f27d2ca7f6d535f7e35dd817493104814423eb48regenerate for schema changes by 2020-07-31
Last Week
Thanks, we’ll try to take a look at this request next week. For programs where it’s critical to receive stop / shutdown event, do you know if there is a workaround that can be used until this is…
Does this issue affect Go 1.13 in addition to 1.14, or was it introduced in 1.14? We need to know this because the minor release policy requires an issue is fixed in all affected supported releases (…
(8 comments) Is there a call to flag.Parse() missing? Consider using UserConfigDir instead. Consider filepath.Join-ing it with "relui" or so. There are some calls to newFileStore with the empty s…
From https://farmer.golang.org#pools: - host-android-arm64-corellium-android: 0/0 (3 missing) - host-darwin-arm64-corellium-ios: 0/0 (3 missing) Their results have stopped showing up on https:…
dmitshur closed a change doc/go1.15: add dd's closing tag3d
dmitshur commented on doc/go1.15: add dd's closing tag3d
This change was bundled into CL 245977, in patch set 2.
dmitshur closed a change doc/go1.15: add "now"3d
dmitshur commented on doc/go1.15: add "now"3d
This change was bundled into CL 245977, in patch set 2.
(2 comments) LGTM, thanks! While many phrases use "now", there are plenty that omit it, so I think this would be fine without it. There's no need to make them all include it. But, this is okay too.
Sounds good. Factored it out into a standalone issue #40519.
(Factoring out comment https://github.com/golang/go/issues/28856#issuecomment-665252612 into a separate issue, since it's slightly different than #28856 and out of scope for that issue.) Some of `…
(1 comment) The change looks reasonable to me, but I'm not closely familiar with the logic so I'll give +1 for now. Is it worth adding a test for this, or okay as is? Will the new tests in CL 24089…
Thanks for reporting. This looks like a bug that needs to be fixed. Where did you get to the URL https://golang.org/doc/articles/wiki/final.go from?
Either rename the `StarGazers` field to `Stargazers`, or add an explicit name override via field tag: ```Go StarGazers struct { TotalCount githubv4.Int } `graphql:"stargazers"` ``` There's…
In a Go release meeting, we noticed issue #40368 likely affects Go 1.13 as well. This needs to be confirmed, and if so, this is the tracking issue for #40368 to be considered for backport to the next…
I think there is a benefit to using this approach as a next step to support linking to module source code. Iterating on this approach in an internal package can help inform the design of an HTTP m…
The https://golang.org/project/ page has a "Version history" section that lists major Go releases that have been released. Prior to [CL 229483](https://golang.org/cl/229483), it needed to be manually…
dmitshur starred in rsc.io/swtch6d
rsc.io is working again now (see https://github.com/rsc/quote/issues/4#issuecomment-665300101). Making cmd/go tests not depend on external services is tracked in issue #28856. I don't think there's a…
The immediate issue has been resolved: ``` $ GOPROXY=direct GO111MODULE=on go get rsc.io/quote/v3 go: downloading rsc.io/quote/v3 v3.1.0 go: downloading rsc.io/quote v1.5.2 go: rsc.io/quote/v3…
@menghanl Fixing rsc.io/quote is being tracked in issue https://github.com/rsc/quote/issues/4.
@hencrice The `GOPRIVATE` environment variable in `go env` output is set to `*`, which tells the go command to consider all modules as private and not to use the module proxy and checksum database fo…
@hencrice Please post the full output of running `go version`, then `go env`, then the exact command you ran that's still giving an error, so we have full information. It should work okay if GOPRO…
There were some additional cmd/go tests failing on the longtest builder because `rsc.io`, `swtch.com`, and `insecure.go-get-issue-15410.appspot.com` domains were not serving Go packages (see #40452).…
@hencrice I can't reproduce this with Go 1.14 with a default configuration: ``` $ go version go version go1.14.6 darwin/amd64 $ cd $(mktemp -d) $ go mod init example.com/m go: creating new go…
dmitshur commented on doc: write Go 1.15 release notes1w
The draft notice is correct. We generally remove it as part of making the final release, not earlier.
Following up on https://github.com/golang/go/issues/38485#issuecomment-647584660. Since then, I found that Gio (/cc @eliasnaur) also sets the `ios` build tag unconditionally (see [here](https://gi…
By now (after some number of days have passed), it says "The current version is go1.14.6." on the About page.
> strange thing is we do receive those collaborators regardless in our response. Maybe the results are incomplete? If you think it's a bug on GitHub's side, it would be helpful to report it to them.…
This false positive issue is very similar to #316. Consider test code like this: ```Go func TestFooAllocs(t *testing.T) { allocs := testing.AllocsPerRun(1000, func() { Foo("bar") }) if a…
Earlier
Overall, I like the plan and the future versions. As discussed over chat, I think you should avoid retroactively giving existing older releases (all but the latest current release, 2020.1.4) a seman…
> I can also confirm I'm getting the data back as expected. So it seems to be something in the lib that is doing some check or magic somewhere after getting the response causing that error regarding …
Thanks for investigating and confirming this is fixed, Hajime.
> However when ran from graphql playground using the same authentication token it works. That is unexpected. > Is there a way I can inspect the generated graphql? Yeah, it's a good idea to confirm…
dmitshur commented on go4.org: Installing go4 error1w
No problem. @melardev Out of curiosity, did you find the previous invalid "github.com/go4org/go4/strutil" import path written down or suggested somewhere? I'm asking because if there was some resour…
dmitshur commented on go4.org: Installing go4 error1w
The fix is to use a matching module path, which is `go4.org`. You can see it declared at the top of the [`go.mod` file](https://github.com/go4org/go4/blob/f5505b9728ddf920bb673137648788c5ac99de1b/go.…
I believe this particular misalignment has been resolved by now. I'm not able to spot it by now. Note that #28643 tracks general readability improvements to the golang.org/x repo view.
Thanks for reporting the problem with `ignore` build tag, that indeed needs to be fixed. Can you please open a separate issue about the problem with `importPathToDir`? It does need to be run inside …
> a bug in the dashboard UI I've looked into it, it's not a trivial mistake, the problem happens due to insufficient data and a more complete fix would need changes to multiple components (the bui…
It turns out it's a bug in the dashboard UI rather than intentional configuration. The `linux-amd64-androidemu` builder is configured to run both on pre- and post-submit builders. There's even a [tes…
Oh, I was misreading the build dashboard. The linux-amd64-androidemu builder is configured run pre-submit trybots, but not post-submit builds. Skipping it with this issue open seems reasonable to …
Do you know since when it became flaky? How often have you seen it? I'm not seeing many (or any) previous failures on the post-submit runs (https://build.golang.org/?repo=golang.org%2fx%2fmobile).…
My intention was to suggest we use #39813 for tracking improvements to the heuristic of when to consider a function as a "factory function". However, this issue seems slightly different, as it's abou…
Closing in favor of aforementioned issue. See https://github.com/golang/go/issues/36642#issuecomment-577908050 for more details about what happened, including the root cause.
The current latest Go release is Go 1.14.6. Clicking the About button at https://play.golang.org now says: > The playground uses the latest stable release of Go. > The current version is [go1.…
It seems the memcached instance has become unhealthy again. I'll look into restarting it for now.
Fixed via [CL 243477](https://golang.org/cl/243477) and [CL 241717](https://golang.org/cl/241717).
dmitshur pushed to master in github.com/shurcooL/home2w
e9ff8b15dd53491dc9974c689c910f34742bdd97indieauth: reject redirects to insecure HTTP protocol
> It is not committed If a very large file or directory is not committed, it would not be a real problem, so `gorelease` reporting that is a false positive as far as I understand. Is there already a…
> it does not reproduce on other modules or with an older version of gorelease, [CL 197299/4](https://go-review.googlesource.com/c/exp/+/197299/4). In the diff between [patch set 4 of CL 197299 and …
dmitshur closed an issue [Question]: url of to download package2w
Hi there, Unlike many projects, the Go project does not use GitHub Issues for general discussion or asking questions. GitHub Issues are used for tracking bugs and [proposals](https://golang.org/s/…
Is this a regression? What are the contents and the size of the directory where you ran `gorelease`? /cc @jayconrod
Now that this change was submitted to the release branch, I'll remove release-blocker label to reduce visual noise when viewing the release history details.
@davecheney 1.14.5 was a security release. 1.14.6 is being released right now (see #40256) and it does include the fix. See backport issue #39636 for more details.
From https://farmer.golang.org: ![image](https://user-images.githubusercontent.com/1924134/87721216-14fda880-c784-11ea-9690-76ab02a37ecc.png) May be similar to #37922. /cc @andybons @cagedma…
@libnat If that issue you found is an issue right now, please open a separate issue to track it. If it's introduced by that CL, please leave a review comment on it. @diegomontoya Only the darwin 32-…
Issue #39233 was related, but for Plan 9. /cc @millerresearch @0intro
``` panic: Fail in goroutine after TestTransportPingWhenReading/two_pings_in_each_serverResponseInterval has completed goroutine 14595 [running]: testing.(*common).Fail(0xc0990500) /workdir/go…
Per comments above, `Expect` is considered to be a "factory function" for `Assertion`, so it's displayed underneath it. The code for this is in `go/doc` (see https://github.com/golang/go/issues/39…
Thanks for reporting. As @go101 pointed out via related issues, this is a heuristic and it's working as intended. `Stat` is considered to be a "factory function", so it's displayed underneath `FileIn…
Thank you for doing that work, @odeke-em. The 1.13 backport issue is still in CherryPickCandidate state, so the release managers will need to decide whether it should be approved for backport. Having…
Thanks! This is how the test fails when `oldlink` binary isn't present: ``` $ go test -v -run=TestOldLink -count=1 cmd/link === RUN TestOldLink link_test.go:558: [/tmp/tmp.AG3oE0Ne/go/…
> A test may fail if the old linker is not present. We could change the test to skip if the binary does not exist. @cherrymui Which test were you referring to? I can try to find anything by tak…
Right now, it's possible to use `releasebot -dry-run -mode=prepare` to run a release locally that doesn't produce any public artifacts or changes state, but only for the beta release type (e.g., `go1…
I've confirmed the package `net` does not import `fmt` nor `unicode`, not even indirectly. It was resolved via [CL 241257](https://golang.org/cl/241257), and [CL 241078](https://golang.org/cl/241078)…
@mknyszek Can you please add a short rationale about why the backport might be needed? (Per [MinorReleases](https://golang.org/wiki/MinorReleases).) Thanks.
@ianlancetaylor Issue #37097 was about a problem on the Go-Release-Cycle page. I spotted a problematic statement in the MinorReleases page; filed #40206 about it.
The https://golang.org/wiki/MinorReleases page currently still says: > "Use a more recent stable version" is a valid workaround, so very few fixes will be backported to both previous issues. Th…
Based on https://github.com/golang/go/issues/34775#issuecomment-628115836: > this issue has existed since Go1.12 and unfortunately because it wasn't a regression but rather a long standing bug …
@dmitshur requested issue #34775 to be considered for backport to the next 1.13 minor release. The original issue exists in 1.13 too, so per backport policy, it must be considered for backporting …
Thanks for clarifying, that's very helpful. In the original issue report, I didn't realize you were using an IDE and could not understand where the error was coming from. > I wish I was already a …
dmitshur closed a change all: modify VERSION file3w
dmitshur commented on all: modify VERSION file3w
This was a test for #30037. It's no longer needed.