M.Lesin
M.Lesin
Finally I figured out cause of that behavior. I'm using http proxy, as it seen from "http://" prefix in my variables. After debugging what is happening in zed, during sign...
Are there any restrictions that require the proxy to be a socks type in order to sign in?
> Do you have access to a SOCKS_PROXY you could try or do you only have an HTTPS_PROXY? I confirm that the socks proxy works, but it's just a coincidence...
workaround until fix will be in place: ```shell cargo update -p tracing-attributes --precise 0.1.28 ```
> As a test/workaround, does installing with `cargo install --locked just` get it working correctly? For me this workaround fixes the issue
Missing this feature makes it impossible to use local ollama (or any other services running in both localhost or local network) if you are behind the proxy.