You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have installed the development version of {gptstudio} (pak::pak("MichelNivard/gptstudio")) and tested if the problem remains.
I have installed the {reprex} and {sessioninfo} packages to be able to run this issue's code snippet pak::pak(c("reprex", "sessioninfo")).
What happened?
I'm trying to use gptstudio and fail and fail and fail again.
I have ollama and use this on vscode and positron without problem
also I have google API (I dont have and use OpenAI)
When load chat windows and set model on it, after submit show error
Relevant log output
Loading required package: shiny
Listening on http://127.0.0.1:5499
ℹ Fetching models for openai service...
✖ HTTP 401 Unauthorized.
• OAuth error
• realm: OpenAI API
✖ No models available
ℹ Fetching models for ollama service...
✔ Got models!
Warning: Error in: API key is not valid
85: <Anonymous>
78: gptstudio_skeleton_build
76: observe
75: <observer>
4: shiny::runApp
3: eval
2: eval
1: .rs.sourceWithProgress
Hi, thanks for reporting! This is duplicate, here is the solution: #230 (comment)
Sidenote: you have the dev version of {rstudioapi}, not {gptstudio}. This is why you don't have the tooltips that were meant to guide you to save after changing settings.
I'm closing this, but let us know if the problem persists.
Confirm setup
{gptstudio}
(pak::pak("MichelNivard/gptstudio")
) and tested if the problem remains.{reprex}
and{sessioninfo}
packages to be able to run this issue's code snippetpak::pak(c("reprex", "sessioninfo"))
.What happened?
I'm trying to use gptstudio and fail and fail and fail again.
I have ollama and use this on vscode and positron without problem
also I have google API (I dont have and use OpenAI)
When load chat windows and set model on it, after submit show error
Relevant log output
Session info
Code of Conduct
The text was updated successfully, but these errors were encountered: