o1-mini models broken in 0.8.63

[Jflick58]

Before submitting your bug report

• I believe this is a bug. I'll try to join the Continue Discord for questions
• I'm not able to find an open issue that reports the same bug
• I've seen the troubleshooting guide on the Continue Docs

Relevant environment info

- OS: macOS
- Continue version: v0.8.63
- IDE version: 1.95.3
- Model: o1-mini
- config.json:
  
    {
      "title": "AVA - o1-mini",
      "provider": "openai",
      "model": "o1-mini",
      "apiBase": "https://ava.amfam.com/api",
      "apiKey": "",
      "contextLength": 128000,
      "completionOptions": {
        "stream": false
      }
    },

Description

I upgraded to v0.8.63 this morning and my o1-mini completions started not to return any output. I was working with it fine prior to restarting the extension to install the update.

I receive no error message, I see nothing in the developer tools console, continue.log is empty. This model is an Azure OpenAI model proxied internally (to conform to standard OpenAI model schemas). Via the proxy, we can see that stream: true seems to always be sent regardless of the completionOptions in config.json.

Looking at the release commits, I'm guessing this is either part of the config json -> yaml conversion or part of the o1 "fixes".

To reproduce

1. Set config with stream set to false.
2. Try to call o1 mini in Continue.

Log output

No debug logs are emitted.

[Sillocan]

I am seeing this as well for o1-preview

[ctwardy]

Possibly related to #3388; this one uses OpenAI directly, vs. Azure OpenAI.

[Jflick58]

Still broken in 0.8.65

[Patrick-Erichsen]

Hi folks, thanks for the notice here. Tracking updates to this issue, and other related issues with Azure after the 0.8.63 release, in this thread: #3477

[Jflick58]

@Patrick-Erichsen I think this is a little bit different as we are using the OpenAI provider to call a proxied API with a standard openai-compatible API while those issues all use the Azure Provider.

[Patrick-Erichsen]

Ah, yes re-reading your original issue description that is clearer. I'm going to keep this lumped in with the other issues just because the o1 updates were made around the same time, and to make sure we circle back. But thanks for the clarification 👍

[sestinj]

@Jflick58 found the problem: #3483

I'm pushing this just to pre-release first rather than including it in the hot fix release for the other Azure problems. This should be available later today

[Jflick58]

Thank you @sestinj