Open julien-h2 opened 1 month ago
Same problem, after the update has been reported error.
For now if you need to get some work done. You can pin the version to a commit from a few days ago (just guessing that something recent broke the plugin)
Add commit
to your codeium plugin config per the lazy spec
Choosing 937667b2cadc7905e6b9ba18ecf84694cf227567
because it's seemingly the last stable version (just guessing that something in the last week broke). see
return {
"Exafunction/codeium.nvim",
commit = "937667b2cadc7905e6b9ba18ecf84694cf227567", -- just guessing the commit sha here
-- ... rest of your config
}
And if you don't want to set and forget this pinned version add check_pinned
per default config example
checker = {
check_pinned = true, --
-- ... rest of your config
},
After I switch to commit 937667b, codeium.nvim reports an error that changes to codeium server crashed
.
After I switch to commit 937667b, codeium.nvim reports an error that changes to
codeium server crashed
.
You'll need to run :Lazy update
to get the older version of the plugin
I manually switched the branch of codeium.nvim to 937667b
And export no_proxy was configured as prompted by other issues.
Before the update, everything was going well.
!Note: codeium server crashed
error exists, headache.
Tried the latest language-server version on my local and it looks more stable for me. Could you try this PR https://github.com/Exafunction/codeium.nvim/pull/233 ?
Tried the latest language-server version on my local and it looks more stable for me. Could you try this PR #233 ?
Which version of commit are you based on?
Tried the latest language-server version on my local and it looks more stable for me. Could you try this PR #233 ?
Seemingly is working for me, will update if not
Tried the latest language-server version on my local and it looks more stable for me. Could you try this PR #233 ?
Which version of commit are you based on?
You'll have to use @aliaksandr-trush's fork of the plugin
return {
"aliaksandr-trush/codeium.nvim", -- forked repo
dependencies = {
"nvim-lua/plenary.nvim",
"hrsh7th/nvim-cmp",
},
config = function()
require("codeium").setup({})
end,
}
Tried the latest language-server version on my local and it looks more stable for me. Could you try this PR #233 ?
Which version of commit are you based on?
You'll have to use @aliaksandr-trush's fork of the plugin
return { "aliaksandr-trush/codeium.nvim", -- forked repo dependencies = { "nvim-lua/plenary.nvim", "hrsh7th/nvim-cmp", }, config = function() require("codeium").setup({}) end, }
You also need to specify correct branch name: branch = "update_server_version"
Tried the latest language-server version on my local and it looks more stable for me. Could you try this PR #233 ?
Which version of commit are you based on?
You'll have to use @aliaksandr-trush's fork of the plugin
return { "aliaksandr-trush/codeium.nvim", -- forked repo dependencies = { "nvim-lua/plenary.nvim", "hrsh7th/nvim-cmp", }, config = function() require("codeium").setup({}) end, }
You also need to specify correct branch name: branch = update_server_version
Pretty sure your branch doesn't exist on the main repo codeium.nvim branches. It'll only exist here
Tried the latest language-server version on my local and it looks more stable for me. Could you try this PR #233 ?
Tried the latest language-server version on my local and it looks more stable for me. Could you try this PR #233 ?
Which version of commit are you based on?
You'll have to use @aliaksandr-trush's fork of the plugin
return { "aliaksandr-trush/codeium.nvim", -- forked repo dependencies = { "nvim-lua/plenary.nvim", "hrsh7th/nvim-cmp", }, config = function() require("codeium").setup({}) end, }
This fork solves the problem, so great.
After experimenting locally, I found that when I switched to this commit, problems began to occur. 891439a
Are you on Windows by any chance?
Are you on Windows by any chance?
no any change. just switch commit.
Thanks for bearing with us as we sort this out. looks like windows users were having issues. We merged in a change, if you all could update and let me know if things work, that would be awesome.
Are you on Windows by any chance?
Mac
@pqn I am on windows 11. I have attached the logs in the original post.
I had the issue on mac and windows. https://github.com/Exafunction/codeium.nvim/commit/17bbefff02be8fd66931f366bd4ed76a76e4a57e fixed it on windows, testing mac now spoke too soon: https://github.com/Exafunction/codeium.nvim/issues/225#issuecomment-2380880628
Pretty sure your branch doesn't exist on the main repo codeium.nvim branches. It'll only exist here
A fork also has branches... his main is 5months old
Thanks for bearing with us as we sort this out. looks like windows users were having issues. We merged in a change, if you all could update and let me know if things work, that would be awesome.
mac user here. not sure what you fixed but commmits after 937667b2 show this issue https://github.com/Exafunction/codeium.nvim/issues/236, pinning install to that commit fixes the problem
There have been a series of updates to the nvim extension recently, please try updating to the latest.
This is my lazyvim configuration and it works very well.
return {
{
"Exafunction/codeium.nvim",
dependencies = {
"nvim-lua/plenary.nvim",
"hrsh7th/nvim-cmp",
},
config = function()
require("codeium").setup({
enable_cmp_source = true,
virtual_text = {
enabled = false,
},
})
end,
},
}
return {
{
"nvim-cmp",
opts = function(_, opts)
table.insert(opts.sources, 1, {
name = "codeium",
group_index = 1,
priority = 200,
})
end,
},
}
Hello, I updated my plugins today and codeium is now broken and keeps spamming me with notifications "Code completion request failed".
I use LazyVim without custom configuration.
I collected the logs, attaching them here. codeium.log.log