Closed CAM-Gerlach closed 5 years ago
Update: I tested changing the ignore settings for the code style analysis, but that did not produce an (immediate) LSP stoppage. However, later, I disabled real-time docstring, code style and code analysis (to test its effect on the autosave issue). Immediately on closing preferences, code and code style analysis disappeared as it should (and I know it was working shortly before), but I still had one docstring analysis warning at the top of the file I was on, and it "froze"/stopped updating as they usually do when LSP stops working.
I immediately pulled the logs, and culled down to the relevant portion where I'm highly confident the crash occurred (I can be 100% sure it didn't occur after, and nearly sure it couldn't have happened before); my speculation is that it happened near the beginning of the resulting output, around or shortly after 11:51:00, which would roughly coincide with when I hit "Ok" in the prefs dialog, Once I document what I have so far here, I'll attempt to repro it again.
Spyder log:
LSP client log (file contents replaced by <file conents>
for brevity):
Server log (file contents replaced as above, and module list, plugin configuration and project/lsp configuration replaced as below):
Description
What steps will reproduce the problem?
I finally had LSP services stop working at a time when I have proper log output. Unfortunately, I can't be sure of the exact time it stopped, as it is difficult to notice exactly when updates stop happening if I'm not explictly watching for it (as opposed to actually using Spyder to get work done or test other bugs).
While I cannot be absolutely sure it did not happen at some time last night, as far as I'm aware I was still getting updates up until the end, and while I was opening and closing other Spyder instances up until shortly before that time (after which I had only one open), I have not done so since, nor have I triggered help or completion (just used real-time style/docstring analysis). I did just update to PyLS 0.24 last night, this was within a couple usage-hours of me having done so.
Nevertheless, I can provide output from the logs for an example completion request. For this test, I navigated away from Spyder, checked the reported time in the logs to ensure I wouldn't be capturing any unrelated output, and then switched to Spyder, pressed
TAB
after the phrasetest_auto
on its own that should generate local completions, and switched away. The results:Spyder log:
LSP client log:
LSP server log:
I can retest it with a fresh Spyder instance that does return completions, if it would be helpful to compare the output. Thanks!
Versions
Dependencies