mirror of https://github.com/golang/go.git
9ab2d800b2
The go command gets mad if go.mod has changed since it started, e.g. because a new dependency was added by a concurrent go list call. Retry loads if they hit a concurrency problem. See the comment for more details. Testing this is awkward. I ran a background script that constantly modified the go.mod file and observed that gopls waited until it was killed and then recovered. Updates golang/go#36772. Change-Id: I5636c99a5a94b415c4a6fbb71869b07e31d3fed0 Reviewed-on: https://go-review.googlesource.com/c/tools/+/216543 Run-TryBot: Heschi Kreinick <heschi@google.com> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Rebecca Stambler <rstambler@golang.org> |
||
|---|---|---|
| .. | ||
| apidiff | ||
| fastwalk | ||
| gopathwalk | ||
| imports | ||
| jsonrpc2 | ||
| lsp | ||
| memoize | ||
| module | ||
| packagesinternal | ||
| semver | ||
| span | ||
| telemetry | ||
| testenv | ||
| tool | ||
| xcontext | ||