Cursor SQLite broken on some setups: [internal] SQLITE_BUSY: database is locked

[Colin]

Hey @5660cd1533ce0acb731c

This is a known gap! Some users have been able to find workarounds, like over in this thread:

Cursor CLI throwing SQLITE_IOERR: disk I/O error

Update! What I checked Disk space/inodes are fine and $HOME is writable. /tmp has correct perms (1777). SQLite integrity check on the DB returns ok. My home lives on a shared filesystem: home on /home/aiops type virtiofs (rw,relatime) What happens With the DB on virtiofs, cursor-agent throws SQLITE_IOERR: disk I/O error. Workaround that fixes it If I move the app data + temp dirs to a local ext4 volume, the error disappears. For example: mkdir -p /var/tmp/$USER/{.local/share,.c…

What’s your primary use-case for running the CLI in Kubernetes? Part of your CI/CD, or something else?