[CON-222] "Headers not defined" in older versions of VS Code

[sestinj]

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:*
- Continue:*
- IDE:VS Code (older versions, don't know exactly the cutoff)

Description

Older versions of VS Code (presumably because they run older versions of Node.js) cause this "Headers not found" error to appear as a popup. Here is an example of this happening to a user. Very reliably, upgrading VS Code solves this problem.

There might be an obvious change we can make to ensure compatibility.

If not, we might be able to handle the error more gracefully.

If neither, it would be useful to have brief documentation to share with folks who encounter the problem (explaining why the Node compatibility exists).

_{From SyncLinear.com | CON-222}

[djgould]

Just tested this and I can reliably reproduce on VSCode v1.70 from July 2022 with continue v0.8.25.

However, I cannot reproduce with the pre-release installation or the dev build so I am assuming this has been fixed somehow. I can successfully talk to ollama.

Reproduction steps:

• download and run VSCode v1.70
• install continue extension (current release v0.8.25) from extensions menu
• Select "Fully local" and click continue
• Headers is not defined message appears
• go to extension page and select "Switch to pre-release"
• reload vscode
• "headers is not defined" does not appear, and the extension works properly with ollama

I don't see any PRs explicitly mentioning a fix for this, so maybe it was inadvertently fixed.