[CON-268] SQLITE_IOERR: disk I/O error

[xiangshoulai]

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:Darwin x64 21.3.0
- Continue: v0.9.198
- IDE: vscode 1.92.2
- Model:
- config.json:

Description

Initialize the boot, after which this problem occurs, but not for every window

To reproduce

No response

Log output

No response

_CON-268

[navels]

I am hitting this as well in one of my projects. Running Continue: Rebuild Index doesn't seem to do anything.

This seems to have resolved it for now:

rm -rf ~/.continue/index

That should probably be documented in the troubleshooting guide as something to try.

[sestinj]

Thanks all for the report! Starting to look into this now and will hopefully have some answers soon. In the meantime either rm -rf ~/.continue/index or restarting the VS Code window may both be workarounds

[robinvalk]

These errors show up all the time for me. Every new vscode window I open results in the same error. rm -rf ~/.continue/index really isn't a solution because it removes the indexes of all my other open windows...

Is continue only supported to work in a single vscode window at the time?

error when indexing:  Error: SQLITE_IOERR: disk I/O error
--> in Database#exec('CREATE TABLE IF NOT EXISTS tag_catalog (\n' +
  '            id INTEGER PRIMARY KEY AUTOINCREMENT,\n' +
  '            dir STRING NOT NULL,\n' +
  '            branch STRING NOT NULL,\n' +
  '            artifactId STRING NOT NULL,\n' +
  '            path STRING NOT NULL,\n' +
  '            cacheKey STRING NOT NULL,\n' +
  '            lastUpdated INTEGER NOT NULL\n' +
  '        )', [Function (anonymous)])
	at new Promise (<anonymous>)

[akshaygulabrao]

Please try using the Mistral AI and see if you can reproduce. I can't reproduce this if I'm using Mistral, but can repro if I'm using Voyage AI.

[saviorand]

Also an issue in JetBrains IDEs, e.g GoLand

[zephyr19]

Still happens.

Steps to Reproduce

1. Open two separate VS Code windows, each on a different project, with Continue enabled in both.
2. In Window A, when the Marketplace shows an update for Continue, click Update and allow VS Code to finish installing the new version, and Restart Extensions.
3. Window B (still running the old Extension Host).
4. Open Index page, an error appears: SQLITE_IOERR: disk I/O error
5. Running Continue: Rebuild Index doesn't seem to do anything

What I’ve Tried

• Reload Window A ⇒ the error still there
• Delete ~/.continue/index ⇒ fixes the problem temporarily, but the next extension update repros the issue.

Expected Behavior

Updating Continue in one VS Code window should not break the extension running in other open windows. Ideally, the extension should handle the mixed-version situation gracefully or prompt for an Extension Host restart rather than hitting an unrecoverable SQLite error.

Notes

From what I can tell, Window B’s old Extension Host still holds a long-lived connection to the SQLite DB while Window A’s freshly updated host tries to run a schema migration or write with WAL mode, causing an exclusive-lock failure that surfaces as SQLITE_IOERR.

Any guidance or upcoming fix would be greatly appreciated—this issue hits me every time I update Continue while multiple VS Code windows are open.

Thanks for your help!

[cbaakel]

I appreciate this thread because at least there's a documented workaround. But also contributing so that this gets more visibility and an eventual fix.