-
Notifications
You must be signed in to change notification settings - Fork 2.5k
Description
App Version
3.22.4
API Provider
OpenAI Compatible
Model Used
text-embedding-3-small
π Steps to Reproduce
I am trying to use the codebase indexing feature with my Azure OpenAI embedding model, using the "OpenAI Compatible" provider option ony Windows machine.
I am consistently receiving a 404 Resource not found error, and after debugging, I think I have isolated the cause. The extension is not sending the mandatory api-version query parameter that the Azure OpenAI API requires for all requests.
Here is a summary of my findings:
The Goal: To connect Roo's codebase indexing to an Azure OpenAI deployment endpoint like:
https://[my-resource].openai.azure.com/openai/deployments/[my-deployment]/embeddings?api-version=2023-05-15
The Problem: The settings UI for the "OpenAI Compatible" provider does not have a field to specify the api-version.
The Proof: I used a local Python server to intercept the request from the Roo extension. I found that the extension constructs the final URL by simply taking the "Base URL" from the settings and appending /embeddings. This leaves no way to correctly add the required ?api-version=... parameter for Azure.
This lack of an api-version parameter causes Azure to reject the request, resulting in the 404 error.
Suggested Solution:
Could you please add a dedicated "API Version" field to the "OpenAI Compatible" provider settings? This would allow users to provide the required version (e.g., 2023-05-15) and enable full compatibility with Azure OpenAI.
π₯ Outcome Summary
404 Resource not found error
π Relevant Logs or Errors (Optional)
Metadata
Metadata
Assignees
Labels
Type
Projects
Status