Open Stanzilla opened 1 year ago
The error reported in output panel should have nothing to do with this issue. Are you using symbolic links for your folders? Could you provide the server logs?
Info on the log file can be found on the FAQ page in the wiki :slightly_smiling_face:
The reset stopped happening after I disabled "cast-type-mismatch", "param-type-mismatch", "assign-type-mismatch", "return-type-mismatch" per my guess above. I attached the last log file. file_home_stan_projects_personal_WeakAuras2.log
You could be running into this: https://github.com/Ketho/vscode-wow-api/blob/master/src/extension.ts#L113
The vscode-wow extension doesn't actually define all globals, instead it reacts to diagnostics about undefined globals and tries to add them as defined. Depending on your exact setup this definition attempt may be going wrong (https://github.com/Ketho/vscode-wow-api/issues/132)
So I have this very strange bug where the VSCode extension starts reporting undefined-globals but when I click on the actual problem report, it goes away.
These globals are defined in a file that is loaded as a library via an extension so I figured I might reach the max workspace files/size limit but even with those set to very high numbers it keeps happening. I can click on all of them to make them go away but the next indexing run (hitting save) will bring them back.
workspace.maxPreload
is set to20000
workspace.preloadFileSize
is set to8000
The repo I tested with is WeakAuras
https://user-images.githubusercontent.com/75278/202040021-d15fda8e-85ce-4055-a39e-d9538f6b5446.mp4
So my next guess was that the LSP just crashes and restarts, I checked the output panel and got this: