tree 69dcc938fb024670cb0751c63239139f7a85b9d5
parent f379f50053db75d84a21d1942546213d8dd0c5db
author Hana <hyangah@gmail.com> 1606961760 -0500
committer Hyang-Ah Hana Kim <hyangah@gmail.com> 1607040295 +0000

src/goLanguageServer: improve automated gopls log collection

Now we report the log collection failure reason when we fail to
capture and sanitize gopls log automatically.
And, we configure the lsp client to show the output channel in
case of error events, and also try to read the trace output
three times just in case the output window wasn't able to be
shown yet. The choice of all the constants here (trying 3 times,
sleeping, 10 or 20 ms sleep) is all arbitrary. Can work or not.
Testing is hard.

The report includes the extension version and the editor name info
to help us checking whether users are using the latest extension
version and the usual editor application.

For golang/vscode-go#984

Change-Id: I6e307314e0556520b76a8e444e6b0f861575efd2
Reviewed-on: https://go-review.googlesource.com/c/vscode-go/+/274449
Trust: Hyang-Ah Hana Kim <hyangah@gmail.com>
Run-TryBot: Hyang-Ah Hana Kim <hyangah@gmail.com>
TryBot-Result: kokoro <noreply+kokoro@google.com>
Reviewed-by: Peter Weinberger <pjw@google.com>
Reviewed-by: Rebecca Stambler <rstambler@golang.org>