-
Notifications
You must be signed in to change notification settings - Fork 14
Can't get assistant to work with openai "Assistant error" #94
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I got image to text working (by setting the URL to "https://api.openai.com/") but when I do STT The error log says this |
Signed-off-by: Julien Veyssier <[email protected]>
@manatwork81 06f695b should fix this. It will be included in the next integration_openai release. For now you can set an empty object as extra params: @jon-bit It's not clear what happens to you. It is most likely a bug in the assistant because integration_openai is not involved when scheduling a job but when the job runs. I'll have a look. |
@jon-bit Found and fixed the issue. Fix is included in v1.0.9 which is out now. Could you confirm submitting an audio transcription task with the picker works now? |
@manatwork81 integration_openai v2.0.1 is out. Invalid values for extra llm params are now correctly handled. |
I still get the error |
Which version of integration_openai are you using?
2.0.0
Which version of Nextcloud are you using?
28.0.4.1
Which browser are you using? In case you are using the phone App, specify the Android or iOS version and device please.
Brave
Describe the Bug
When I have the asstent to get requests from open ai I get:
"Text generation error: Failed to run or schedule a task"
on most things (but not all). When I to STT I get
and if I use the quick app in next cloud instead of the builtin tools in files I get
Assistant error
Expected Behavior
it does Textgen or STT
To Reproduce
install openai integration app and set to the API to anything (blank, "https://api.openai.com", "https://api.openai.com/v1/" is what I tried) and try any AI things. It won't work(at least for me).
The text was updated successfully, but these errors were encountered: