Open Godfather95 opened 1 month ago
Uh oh - there is a way to select the settings you want at the bottom: Have you tried switching these? FWIW, we will be adding defaults in a more prominent place soon.
@sethjuarez Yeah, I tried it, and I even copied the settings to be the "non default". But no matter which model configuration I select, I always get the error.
For me as well. I tried changing the configuration, but always getting the error.
the same problem, it always use type azure_openai even if I set openai instead
I am experiencing the same issue (even with hardcoded values, not being read from environment).
oof - ok - I will look into it - I am adding some features to the extension this week/next. There's a couple of invokers I need to add to make this work
I am getting something related, I changed the user settings to add my deployment and after that I start getting this error I reverted the changed, uninstall and install again my extension and nothing have worked so far. I am using the API Key Endpoint pair in my .env file
I am getting something related, I changed the user settings to add my deployment and after that I start getting this error I reverted the changed, uninstall and install again my extension and nothing have worked so far. I am using the API Key Endpoint pair in my .env file
It seems the problem has been resolved. I traced back the changes made and reverted them. The issue appeared to be related to the workspace settings. Once I deleted the .vscode folder that generates when you open the workspace settings file, the problem was resolved.
Same issue here
We read the setting from prompty.currentModelConfiguration.
In some cases VSCode saves to .vscode/settings.json.
And some cases it's saved to your user levels settings.
@BartNetJS @AnaTipps @perkops @abakumovoleg @anuraj @Godfather95 , can you let me know what's your case? I'll see how to make this less problematic
In my case, aside from multiple configuration files, the endpoint was overridden in the yaml file itself. I copied it from a sample and didn't notice the setting and didn't remove it and it overrode my settings files. A strategy I've used in the past is to have a way to retrieve all of the current settings to see if they're what is expected. If a value isn't what you expect, it's just a matter of tracking down the source of the unexpected value. Also, a document explaining all the possible places values can be read from and in what precedence order is also useful.
Same issue here
I am using the following configuration in settings.json:
When running a
.prompty
file, I get the following info message in the Prompty Output:info] Missing prompty configuration setting: MissingDeployment. Your setting is {"name":"default","type":"azure_openai","api_version":"2023-12-01-preview","azure_endpoint":"https://<EndpointName>.openai.azure.com/","api_key":"<APIKEY>"}
It seems the Extension doesn't even read the "azure_deployment" from the settings.