-
Notifications
You must be signed in to change notification settings - Fork 58
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Codeium throws errors on large files #20
Comments
I'm having trouble reproing this issue. How are you disabling TS? |
I am disabling it directly in the configuration like this (basically what treesitter suggests in their docs https://github.com/nvim-treesitter/nvim-treesitter/blob/master/doc/nvim-treesitter.txt#L117 )
Now that I reread the issue again it was slightly misleading, what I am actually doing is disabling the |
Not sure if this is related, but also getting an error from the command window (
Edit: Not related to this, created separate issue |
I got the same error, but in my case the problem was not in the treesitter highlight, but in the big files themselves. I was having this problem on a file with around 3500 lines and when I deleted around 1000 lines the problem was gone. On the other hand, I took a plain text file and copy/pasted until I got to about 5000 lines and the problem started. I was also able to reproduce this in .zshrc and Lua files. Edit: the problem is Full error
|
I'm getting this same error. I think my issue is related to @brunolpsousa where I'm getting this on large C# files. Files that don't work:
Working files
It looks like the issue is tied more to the number of lines than anything in my case. Once the file gets to be around 600 lines it starts to fail in C#. I'm running on Windows. I can provide any logs as needed |
The fix is we probably have to switch the curl to accept data from stdin instead of passing it as an argument. |
Still happening in Apr 2024 :( |
Same thing for me. Getting this error at big yml files, than any completion call on any file raise this error |
Edit: Realizing I still experience the issue if I open the too big file along with a smaller one. The codeium source appears to send other buffers as additional context. That's a big enough issue to where I guess I just have to disable the extension for now. I was experiencing this issue too. I ended up configuring nvim-cmp per buffer, and excluding codeium on files over 100KB. From above comments, that number should probably be lower, but this works for me at the moment. You can see the change in my config here. I referred to the nvim-cmp documentation on this page: https://github.com/hrsh7th/nvim-cmp/wiki/Advanced-techniques#disabling-completion-in-certain-contexts-such-as-comments This obviously doesn't fix the root issue, and it would be nice if codeium worked in large files, but it will keep your neovim usable. |
Following this issue for updates: Exafunction/codeium.nvim#20
I made a PR to fix this. Can anyone test it and provide feedback? |
Yup, I can confirm that it works. I just changed Exafunction to brunolpsousa in my config and reinstalled the plugin. Awesome stuff, hope it gets merged soon! Edit: Let me know if you're looking for any specific feedback. I tried it out with a file over 1MB. |
I'm getting this problem too. It doesn't seem to be for big files necessarily, but seems to come when I have many tabs open/leave neovim on for long periods of time. I switched to brunolpsousa and ran Lazy sync but still get this problem, am I doing something wrong? |
You don't need to use my branch because it has already been merged. Make sure your Lazy config is not locked to a specific commit or any other version control. If it still doesn't work, I think it would be better to open a new issue and provide logs. |
Hi, I am playing around with this plugin and found an issue: I have treesitter configured to disable text highlight in big files (in those cases it is too slow and makes the editor hang for a couple of seconds after each key stroke, falling back to the regex parser solves this issue) and it seems that doing this makes your plugin break with the following error
(api key and text have been cropped out just to be safe)
If I enable treesitter highlight again the error disappear but then the editor became unusable, it would be great to fix this issue.
Let me know if you need something else to help debug this issue :).
The text was updated successfully, but these errors were encountered: