| commit | 56b0b28a00f70e5545e8b1caf3ceb7c197d1924a | [log] [tgz] |
|---|---|---|
| author | Muir Manders <muir@mnd.rs> | Tue Dec 10 11:29:58 2019 -0800 |
| committer | Rebecca Stambler <rstambler@golang.org> | Thu Dec 19 19:20:50 2019 +0000 |
| tree | 467003fd7bee9b4cd2ffab56f77137243486e324 | |
| parent | bdebc07e97384e59eb825068a8c943bae662554c [diff] |
internal/lsp: put verbose go/packages output behind verboseOutput flag On startup gopls runs go/packages over the entire workspace. The log message in question outputs each package found along with all the package's filenames. Obviously in a large project this produces an incredible amount of output. Fix by putting the log message behind the "verboseOutput" flag when invoking go/packages in the "dir/..." mode. I also added the go/packages "query" string to the once-per-go-packages-call log message so it is more useful. Change-Id: I651419e34a855325056bca6720eda8671f7d5fa8 Reviewed-on: https://go-review.googlesource.com/c/tools/+/210739 Run-TryBot: Muir Manders <muir@mnd.rs> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Rebecca Stambler <rstambler@golang.org>
This subrepository holds the source for various packages and tools that support the Go programming language.
Some of the tools, godoc and vet for example, are included in binary Go distributions.
Others, including the Go guru and the test coverage tool, can be fetched with go get.
Packages include a type-checker for Go and an implementation of the Static Single Assignment form (SSA) representation for Go programs.
The easiest way to install is to run go get -u golang.org/x/tools/.... You can also manually git clone the repository to $GOPATH/src/golang.org/x/tools.
This repository uses Gerrit for code changes. To learn how to submit changes to this repository, see https://golang.org/doc/contribute.html.
The main issue tracker for the tools repository is located at https://github.com/golang/go/issues. Prefix your issue with “x/tools/(your subdir):” in the subject line, so it is easy to find.