VSCode extension setttings are not read correctly

[Godfather95]

I am using the following configuration in settings.json:

{
      "name": "default",
      "type": "azure_openai",
      "azure_deployment": "gpt-35-turbo",
      "api_version": "2023-12-01-preview",
      "azure_endpoint": "${env:AZURE_OPENAI_ENDPOINT}",
      "api_key": "${env:AZURE_OPENAI_API_KEY}"
},
{
      "name": "gpt-3.5-turbo",
      "type": "openai",
      "api_key": "${env:OPENAI_API_KEY}",
      "organization": "${env:OPENAI_ORG_ID}",
      "base_url": "${env:OPENAI_BASE_URL}"
}

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.

[sethjuarez]

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.

[Godfather95]

@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.

[anuraj]

For me as well. I tried changing the configuration, but always getting the error.

[abakumovoleg]

the same problem, it always use type azure_openai even if I set openai instead

[perkops]

I am experiencing the same issue (even with hardcoded values, not being read from environment).

[sethjuarez]

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

[AnaTipps]

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

[AnaTipps]

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.

[BartNetJS]

Same issue here

[wayliums]

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

[MikeYeager]

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.

[MikeStall]

Same issue here