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
It happens when I re-start VSCode, because the check whether go files exist (recursively) times out
Go extension activated on three of them (the fourth was a flat folder, pretty much), Dart on two of them (checks up to four-deep, instead of **/). Those were the only two that activated because of that timeout.
The python extension had "contains **/*.py" ahead ago and after receiving multiple complaints, they only have "onlanguage" (which causes confusion among students). Eventually, I found out that their workaround was to look for an empty file ("mspythonconfig.yaml" or sth -- confusing name, don't think it serves any other purpose) in root folder only..
Per microsoft/vscode#73656 (comment), maybe we could try limiting the depth of our search. Frankly, if no go files are contained within a few layers of directories, we'd probably be better of not starting the extension (I assume it would be started when the first Go file is opened).
@findleyr's suggestion is reasonable and we can change this to Dart's approach (only look at only a couple of layers).
Reading the original issue microsoft/vscode-go#2821
I think the fix should've been just adding more "onCommand:..." commands instead of eager loading.
We should consider to drop this eager loading like Python - however, currently, gopls's initial package loading may not be prompt enough for a large project so we will continue to activate the extension if .go files are found in the top levels.
Reported externally.
Looking into the history of the Go extension, I found this rule was added by microsoft/vscode-go#2859 to address microsoft/vscode-go#2821
User-visible impact
Internal impact
Workaround for affected users - explicitly enable/disable the go extension for the workspace based on need through the extension view.
The text was updated successfully, but these errors were encountered: