[Bug]: Being able to persist my default model which is not the OpenAI key (fabric default) #767
Closed
1 task done
Labels
bug
Something isn't working
What happened?
[Bug]: Fabric Dependency Issues with gRPC and Google Cloud Libraries] #747 (comment))
#747
This is a bug fix and feature enhancement. Why is this a bug in my eyes since it is not flexible enough to handle variations on a theme to be persisted in the shell and being able to reset the changeDefaultModel and restart the shell.
There needs to be a way to persist the DefaultModel in fabric --changeDefaultModel based upon the --changeDefaultModel command.
I only want to use Google's models/gemini-1.5-pro and ollama models. I want exclude for the time being OpenAI (fabric default) and Claude.ai.
In the re-installation process
1.fabric --listmodels and found models/gemini-1.5-pro
1.fabric --changeDefaultModel models/gemini-1.5-pro
###At this point the gRPC error, was still occurring but I was getting answers from fabric
Once, I reboot OpenAI took precedence and returned the error "Error: Client error '401 Unauthorized' for url 'https://api.openai.com/v1/models'". This reminds me of the "Harry Belafonte & Odetta - A Hole in the Bucket: "https://www.youtube.com/watch?v=xVAvMIhvqfk"
Also, add as many keys as you like but have a way to reset a combination of keys which are dynamically persisted but can be changed and restart the shell and happy fabric-ing to handle as an example (Fabric: This OPENSOURCE AI Framework can AUTOMATE YOUR LIFE & ANY TASK (Setup with Ollama & Groq) : "https://www.youtube.com/watch?v=Iup3-Jvkrhg" ) as a permutation of the ability to reset a combination of keys
Reboot error : I followed the suggested format a similar way described by Joshua Fuller
After a reboot, I get this error "Error: Client error '401 Unauthorized' for url 'https://api.openai.com/v1/models'
For more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/401"
Full Uninstall and Reinstallation:
Uninstalled fabric using pipx: pipx uninstall fabric
Version check
Relevant log output
Relevant screenshots (optional)
No response
The text was updated successfully, but these errors were encountered: