Hello, I am currently in a linux environment on a cloud machine.
Currently, I'm just launching up sourcekit-lsp like this path1/path2/sourcekit-lsp -index-store-path path_to_index -index-db-path path_to_db `
Nothing appears on the terminal after that, and my assumption is that it kicked off fine by checking it out with ps aux | grep sourcekit-lsp.
Now, I know for a fact that there are valid records/unit files in the path_to_index. I was under the assumption that after sourcekit-lsp kicks off, it examines the file path, and will start writing out the db afterwards to the designated db path. It seems like none of it is being done, and was hoping I could get some help in figuring this out. My apologies, I'm very new to this. I will continue to dig into this myself as well, but was hoping someone could correct my understanding if something is off. Thanks all!
You can view SourceKit-LSP logs in ~/.sourcekit-lsp/logs. If you don’t find anything obvious in there, could you create a diagnostic bundle using sourcekit-lsp diagnose and attach that so I can have a quick look?
Also:
Which version of Swift are you using?
What kind of project are you using (compile_commands.json, SwiftPM projects, build server)?
I guess fwiw, I dont even see the logs so I assume it's not even starting. Assuming I have path_to_sourcekit, doing path_to_sourcekit -help does print out the help options. Hence, what I'm doing is ``path_to_sourcekit -index-db-path path1 -index-store-path path2` here, and after running the command in the terminal, nothing occurs. I can exit out using ctrl + c though to be able to type in my terminal again.
Do I need to pipe in some sort of initialize request to the sourcekit-lsp? I didn't find any instructions on doing this. No logs so far, so I'm assuming it didnt really "start up"