Rob Findley 45849e8256 internal/lsp/lsprpc: wait for the handshake before running clientConn ... By running the client connection before the forwarder-remote handshake completes, we introduce a race in the TestDebugInfoLifecycle: the editor may connect and initialize before the handshake, and assertions on the debug state fail. Requiring that the handshake complete before running the client connection fixes this flakiness. It also seems like a good thing to have the handshake complete before proceeding with any LSP. Fixes golang/go#37444 Change-Id: I07187797b4759bcaf99f5b0a0b3cd7ac7de34f43 Reviewed-on: https://go-review.googlesource.com/c/tools/+/220903 Run-TryBot: Robert Findley <rfindley@google.com> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Rebecca Stambler <rstambler@golang.org>		2020-02-25 18:38:23 +00:00
..
autostart_posix.go	internal/lsp/lsprpc: automatically resolve and start the remote gopls	2020-02-24 22:51:55 +00:00
autostart_windows.go	internal/lsp/lsprpc: automatically resolve and start the remote gopls	2020-02-24 22:51:55 +00:00
lsprpc_test.go	internal/lsp/lsprpc: clean up client session on disconnection	2020-02-24 23:23:05 +00:00
lsprpc.go	internal/lsp/lsprpc: wait for the handshake before running clientConn	2020-02-25 18:38:23 +00:00
telemetry.go	internal/lsp: refactor LSP server instantiation	2020-02-06 23:12:37 +00:00