tree 42440b612dd4e94b28a2b48df02695f668a382af
parent 3c8da71e1b573045109ae4ff255bad787a457aff
author Rebecca Stambler <rstambler@golang.org> 1631227869 -0400
committer Hyang-Ah Hana Kim <hyangah@gmail.com> 1631733197 +0000

[release] goLanguageServer: track language server's restart history

And show it in automated issue reports. This will allow us to see if
crashes were potentially caused by a bad restart. Sometimes we notice
crashes that don't have any associated gopls stack traces, so we were
wondering if there is something about the way that we do restarts that
causes these issues.

Automated issues will list when and why the language server was
restarted, as well as when the issue was suggested.

Change-Id: I298cb4a4931bfedeb75bada446ddbc480eec1501
Reviewed-on: https://go-review.googlesource.com/c/vscode-go/+/348973
Reviewed-by: Hyang-Ah Hana Kim <hyangah@gmail.com>
Trust: Hyang-Ah Hana Kim <hyangah@gmail.com>
Trust: Rebecca Stambler <rstambler@golang.org>
Run-TryBot: Hyang-Ah Hana Kim <hyangah@gmail.com>
TryBot-Result: kokoro <noreply+kokoro@google.com>
(cherry picked from commit c71634cde6524a35566e9c0ec49a4b76b4560b33)
Reviewed-on: https://go-review.googlesource.com/c/vscode-go/+/350139
Reviewed-by: Rebecca Stambler <rstambler@golang.org>