Resolve proxy error when adding Azure OpenAI model #4277
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
close #3993 #4202
Description
This pull request corrects an error that occurs when adding an Azure OpenAI model while using a proxy.
The error stems from the fact that the Azure SDK's ProxySettings requires the proxy host to specify the schema (such as http://) as part of the hostname.
For reference, please see the relevant code snippet in the Azure SDK for JavaScript:
https://github.com/Azure/azure-sdk-for-js/blob/main/sdk/core/ts-http-runtime/src/policies/proxyPolicy.ts#L125-L132
Additionally, to verify this fix, I adjusted the dependency of core to use the local
@continuedev/openai-adapters
package.This was done by modifying the core package's package.json to include the following dependency:
"@continuedev/openai-adapters": "file:../packages/openai-adapters"
Error Logs
Checklist
Testing instructions
To validate the fix for the proxy error when adding an Azure OpenAI model, please follow these steps:
Launch VSCode using the command file: Double-click the vscode-proxy.bat file to launch VSCode with the proxy settings.
Add an Azure OpenAI model: In VSCode, attempt to add an Azure OpenAI model. With the fix, this should now be successful, and you should not encounter the proxy error.