Title: Limiting the number of processes in codeium.vim about codeium.vim HOT 12 OPEN

@ZSaberLv0 If curl is hanging, maybe you can try adding an argument like --max-time to the invocations of curl in the plugin. Is the service working otherwise? If we need to investigate further maybe you can make a new issue, seems like this is sufficiently different.

from codeium.vim.

@chrisgrieser there will always be exactly 2 processes actually; one is the child process of the other.

from codeium.vim.

There should only be one codeium process per nvim process. The fact that you have so many suggests that maybe many processes are not being killed when nvim exits. I can look into this.

from codeium.vim.

Curious if #102 fixes this issue for you. We now explicitly call jobstop upon VimLeave which should kill the language server process.

from codeium.vim.

Indeed, after exiting Neovim, all processes of Codeium are terminated. However, my typical usage scenario involves opening two panes in Tmux - one to open Neovim and one to run a program, as shown in the figure below. Since Codeium uses too many processes, I have to exit Neovim in order to run the program with multithread. Therefore, I hope to limit the number of processes so that I can run multi-threaded programs without closing Neovim.

from codeium.vim.

Hmm, I'm not sure why we're launching so many processes then.

can you add the following line to function! s:ActuallyStart() abort inside codeium.vim/autoload/codeium/server.vim?

call codeium#log#Error('Starting language server.')

And then the following line to your init.nvim file:

let g:codeium_log_file = '/home/<user>/codeium.log`

Then tail the log file and let us know what actions cause Starting language server to get printed?

from codeium.vim.

Sorry for the late reply. I have attached the log file.
codeium.log

from codeium.vim.

got similar issue, codeium created many curl task during usage, but all of them would exit properly when vim exited

from codeium.vim.

@ZSaberLv0, @xuwei152 have you solved this issue?

from codeium.vim.

No, the issue is still there. I have to close neovim when I use a multithreading program like fzf.

from codeium.vim.

same for me, however, for me, it is always exactly two codeium processes running:

neovim 0.9.1 (homebrew)
neovide 0.11.0 (homebrew)
macOS 13.4.1 (M1)

from codeium.vim.

I encountered the same problem. I just installed codeium today. I am using neovim. What configuration should I do to limit the number of processes?

from codeium.vim.