Closed cxwx closed 6 months ago
The problem is that the codeium local proxy does not use curl, but the plugin does. I'll add support for proxy config.
I have the same issue, codeium can not work when proxy is running,disable the proxy agent can work normally.
The language server binary should respect environment proxy variables. Maybe you can try setting something like HTTP_PROXY
?
Yes, i export the http_proxy=http://127.0.0.1:7890/
and https_proxy=http://127.0.0.1:7890/
in the terminal,codeium can not work. If i cancel the environment variables works well.
In my case, the encoding type of the http response is gzip, so my proxy server assume it's transfer-encoding is chuncked, and removed the content-length in the header. As a result, all curl process are hang
BTW, it's wired the response of languageserver use gzip without chuncked
If the curl component is having a problem, you can use noproxy
in .curlrc
to avoid localhost/127.0.0.1/codeium.com subdomains. Similarly, the Codeium binary should respect the NO_PROXY
environment variable. And if you want these components to respect your proxy settings, they will do so by default. The curl dependency is not likely to disappear.
can we use vim.g.copilot_proxy like we do with copilot using parameters similar to proxy to determine whether to use a proxy
Hi all, I found that if I set my
.curlrc
with proxy the codeium not work correctly, because my proxy is not connect to interenet, So how could I avoid that? Could I set codeium itself, not using system curl?