Thank you for the bug report
Bug description
As described in StevenLooman/magik-tools#551.
The Magik LSP writes a file which can take some time to write to disk (~10MB). The process of writing this file, gets stopped too early, causing an incomplete file. On next startup the file is corrupted and can't be used by the LSP anymore.
Steps to reproduce
- Use the Magik LSP
- Open a Magik project (for example: https://github.com/StevenLooman/magik-tools/tree/develop/sw_type_dumper)
- Wait for the LSP to have fully indexed the workspace
- Shutdown the workspace (via
M-x lsp-shutdown-workspace)
- The written JSONL is corrupted
Expected behavior
The written JSONL is okay after shutting down the workspace
Which Language Server did you use?
lsp-magik
OS
Linux
Error callstack
Anything else?
The same LSP in combination with VSCode didn’t have this issue.
Thank you for the bug report
lsp-moderelated packages.M-x lsp-start-plainBug description
As described in StevenLooman/magik-tools#551.
The Magik LSP writes a file which can take some time to write to disk (~10MB). The process of writing this file, gets stopped too early, causing an incomplete file. On next startup the file is corrupted and can't be used by the LSP anymore.
Steps to reproduce
M-x lsp-shutdown-workspace)Expected behavior
The written JSONL is okay after shutting down the workspace
Which Language Server did you use?
lsp-magik
OS
Linux
Error callstack
Anything else?
The same LSP in combination with VSCode didn’t have this issue.