Robert Findley f1bb5ca08f internal/lsp/cache: report a critical error when go.work is invalid ... When a go.work file fails to validate, the workspace is left in an invalid state: we will detect that the workspace is defined by the go.work, but will not actually parse any active modules. This should be a critical error. Fix this by adding allowing the workspace to surface critical errors via a new cache.workspace.criticalError method. Additionally: - only build the workspace mod file in workspace.build if the mode is fileSystemWorkspace (in all other modes the modfile is already determined) - rename workspace.invalidate to workspace.Clone, to be consistent with other data structures - rename CriticalError.DiagList to CriticalError.Diagnostics - add several TODOs for observations while reading the code - create a new file for regtests related to broken workspaces - make the regtest sandbox panic when duplicate paths are present in the sandbox file set (an error I made while writing the test) Updates golang/go#53933 Change-Id: If8625ab190129bc9c57e784314bc9cc92644c955 Reviewed-on: https://go-review.googlesource.com/c/tools/+/417593 Reviewed-by: Hyang-Ah Hana Kim <hyangah@gmail.com> gopls-CI: kokoro <noreply+kokoro@google.com> TryBot-Result: Gopher Robot <gobot@golang.org> Run-TryBot: Robert Findley <rfindley@google.com>		2022-07-27 18:59:40 +00:00
..
builtin_test.go	internal/lsp: don't call PackagesForFile on builtin.go	2021-04-29 13:06:21 +00:00
diagnostics_test.go	internal/lsp/cache: report a critical error when go.work is invalid	2022-07-27 18:59:40 +00:00
undeclared_test.go	internal/lsp/cache: fix incorrect detection of useless code	2021-10-14 14:04:14 +00:00