-
Notifications
You must be signed in to change notification settings - Fork 15
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
Knowledge - Not able to ingest pdf files with images using Azure OpenAI provider. #648
Comments
@thedadams This should be addressed by the revamp to model listing that you did the backend for and @ryanhopperlowe is doing the frontend for? |
Yes, that's correct. |
UI portion should be fixed by #744 |
#744 is merged to main now. @thedadams - can you move this to |
@ryanhopperlowe backend is already in, right? you would not have been able to do frontend without it |
Tested with latest version
This issue is still reproducible.
I see this error when ingesting knowledge file - Reunion-Under-The-Stars.pdf
Note - I am starting the otto server with invalid openai api key in this case. Ingesting Holiday List_2024.pdf succeeds. |
The final fix was: obot-platform/tools#261 |
Steps to reproduce the problem:
OPENAI_API_KEY
)gpt-4o
andtext-embedding-3-small
models toAzure OpenAI provider
Ingestion of this file succeeded.
Ingestion of this file, fails with following error which shows
OPENAI_API_KEY
being used for loading the documents.failed to load documents from file "ws://Reunion-Under-The-Stars.pdf" using loader "": error sending image to OpenAI: OpenAI OCR error sending request(s): retry limit (5) exceeded or failed with non-retriable error(s): #1/5: 401 <{ "error": { "message": "Incorrect API key provided: sk-test. You can find your API key at https://platform.openai.com/account/api-keys.", "type": "invalid_request_error", "param": null, "code": "invalid_api_key" } } > (err: )
Expected Behavior:
Ingestion of file should succeed by using Azure OpenAI provider model.
The text was updated successfully, but these errors were encountered: