twinnydotdev / twinny

The most no-nonsense, locally or API-hosted AI code completion plugin for Visual Studio Code - like GitHub Copilot but completely free and 100% private.
https://twinny.dev
MIT License
2.3k stars 126 forks source link

Configured providers but twinny not sending any requests to provider. #242

Open Duoquote opened 2 months ago

Duoquote commented 2 months ago

Describe the bug I have setup the following providers and I checked with curl that /api/generate endpoint on http://duodesk.duo:11434 works, the extension shows loading circle but is not sending any requests. Also tried setting Ollama Hostname setting to duodesk.duo, but no luck.

To Reproduce Just added the providers I have attached.

Expected behavior Should work with the providers I have I think?

Screenshots image

Logging Logging is enabled but not sure where am I supposed to see the logs, checked Output tab but there is no entry for twinny.

API Provider Ollama running at http://duodesk.duo:11434 in local network.

Chat or Auto Complete? Both

Model Name codellama:7b-code

Desktop (please complete the following information):

Additional context

Duoquote commented 2 months ago

I was looking at other issues and saw where I could see the logs, the log is as follows: image

Looks like hostname is set incorrectly, how do I change it?

rjmacarthy commented 2 months ago

Maybe try a restart? The settings look correct to me. Also in the extension settings change the Ollama settings too. Click the cog in the extension header, there are some api settings for ollama in there too.

randomeduc commented 1 month ago

How can I check some logs? Because I have the same problem on Windows, I'm running VS Code from WSL:Ubuntu

  1. Install Ollama and check if is running at http://localhost:11434

imagen

  1. Install the models imagen

  2. Install and configure the vscode extension Settings imagen

Providers imagen

  1. Test the chat imagen

Got this message from vs code dev tool imagen

But the loading spinner keep there, any help? Also try 127.0.0.1 as host but same results.