Describe the bug
Hello. There seems to be an issue with the new ollama implementation in which glass has difficulty querying the ollama api. I'm not too familiar with the structure of this app but my guess is that glass can see the ollama end point, but the actual state of which AI model being used is out of order. Taking a look at the printout modelStateService.js doesn't pick up on the fact that ollama is the service being used.
To Reproduce
Steps to reproduce the behavior:
- Go to welcome screen (I personally did this by going to the 3 dots and clicking disable whisper. That seemed to send me to the welcome screen)
- Click on "Enter your api keys" under "Use Personal API keys"
- Select Ollama (Local)
- Select a SST provider. I went with a local whisper, but it I believe it has no impact on this bug.
- Confirm
- Click ask
- Enter a prompt
- Nothing appears, but there is a console print out.
Expected behavior
A response back from the ollama end point, but it was empty.
Screenshots
Printout:
Evidence that the state is null/not selected from the front end:
Environment
- OS: macOS
- App Version: 0.2.4
Additional context
I had ollama installed before I had tried running this app.
Describe the bug
Hello. There seems to be an issue with the new ollama implementation in which glass has difficulty querying the ollama api. I'm not too familiar with the structure of this app but my guess is that glass can see the ollama end point, but the actual state of which AI model being used is out of order. Taking a look at the printout modelStateService.js doesn't pick up on the fact that ollama is the service being used.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
A response back from the ollama end point, but it was empty.
Screenshots
Printout:
Evidence that the state is null/not selected from the front end:
Environment
Additional context
I had ollama installed before I had tried running this app.