You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
looks like it's possible to reach the ModuleResolver.moduleCacheCache before initialization.
from discussion with @heschi, it might be OK to eagerly initialize in ProcessEnv.GetResolver: presumably by the time we get the resolver we actually need it. There may be edge cases, however.
findleyr
changed the title
gopls: automated issue report (crash)
x/tools/gopls: race to ModuleResolver.moduleCacheCache
Nov 5, 2021
gopls version: v0.7.3
gopls flags:
update flags: proxy
extension version: 0.29.0
go version: devel go1.18-d032b2b2c8
environment: Visual Studio Code darwin
initialization error: undefined
issue timestamp: Sun, 31 Oct 2021 22:55:38 GMT
restart history:
Fri, 29 Oct 2021 12:19:24 GMT: activation (enabled: false)
Sun, 31 Oct 2021 22:31:02 GMT: installation (enabled: true)
Sun, 31 Oct 2021 22:33:56 GMT: installation (enabled: true)
ATTENTION: PLEASE PROVIDE THE DETAILS REQUESTED BELOW.
Describe what you observed.
OPTIONAL: If you would like to share more information, you can attach your complete gopls logs.
NOTE: THESE MAY CONTAIN SENSITIVE INFORMATION ABOUT YOUR CODEBASE.
DO NOT SHARE LOGS IF YOU ARE WORKING IN A PRIVATE REPOSITORY.
<OPTIONAL: ATTACH LOGS HERE>
The text was updated successfully, but these errors were encountered: