db: server serves before schema migration completes ("table session_inbox has no column named type") #60724

Activity

1. opencodejr commented on Oct 30, 2026

   

   opencodejrBot

   on Oct 30, 2026

   Contributor

   More actions

   Thanks for the detailed report!

   I looked through the OpenCode v2.2.4 source and couldn't find anything that creates either kind of file:

   • .!<pid>!<name> temp files: OpenCode's temp-then-rename writes use names like <file>.<pid>.<uuid>.tmp or <file>.<pid>.tmp, never .!<pid>!<name>. Some of the files you list are also never written through a temp file by OpenCode, e.g. git's own snapshot/<id>/objects/info/packs, log/opencode.log and the .vscodeignore inside the extracted eslint package. A pattern like this usually comes from an external tool that copied, synced or backed up the whole directory around 06:28.
   • opencode.db.corrupted-backup-* / opencode.db.pre-v2migration-backup-*: v2 has no code that writes DB copies with these names.

   To work out where they came from, could you tell us, briefly and in your own words:

   1. Was anything else touching ~/.local/share/opencode around 06:28 and 06:44–07:54 that morning? For example a backup or sync tool (Time Machine, iCloud/Dropbox, rsync, Carbon Copy Cloner), a manual copy or restore, or an AI agent or script you asked to repair the database after the session_inbox has no column named type errors.
   2. Did you run the v1 CLI (1.18.31) on this data directory around that time?
   3. If you still have the logs from then (~/.local/share/opencode/log/), please share any lines that mention these backup files or a database recovery or migration.

   You can reply here, or edit the issue. If you edit it, please also leave a comment saying you've updated it so we know you're done.

   Related issues, ordered by how closely they relate (none of them reports this exact problem):

   • storage: opencode.db at ~687 MB with 77.9% of the file in a single session.revert cell, and desktop drafts.sqlite at 153 MB that is 99.5% free pages #55282: large opencode.db / data-directory growth on v2
   • storage: base64 image tool outputs dominate opencode.db (538 MB of 587 MB) #58436: image tool outputs bloating opencode.db
   • SQLite DB corruption + SQLITE_BUSY lock storm when many agents run concurrently with $HOME on a shared/parallel filesystem #56282: SQLite DB corruption on v2
   • Snapshot repo bloats to 15 GB in 11.5 h on v2.0.27 (latest): 334k loose objects + tmp_obj_*/tmp_pack_* garbage; maintenance gc ineffective #55010: leftover temp files bloating the snapshot repo
2. opencodejr

   added

   triaging

   on Oct 30, 2026
3. carlsuburbmates commented on Oct 30, 2026

   

   carlsuburbmates

   on Oct 30, 2026

   Author

   More actions

   Thanks — you're right, and I verified it rather than assuming.

   1. What touched the directory. Those filenames came from an AI agent session I ran on this machine to recover the database after the session_inbox has no column named type errors — not from OpenCode. I checked directly: the only log lines naming opencode.db.corrupted-backup-* / opencode.db.pre-v2migration-backup-* are from my own du command. There is no OpenCode log entry about a database recovery, corruption, or backup creation, and no code path that emits .!<pid>!<name> — the temp names I saw don't match <file>.<pid>.<uuid>.tmp.

   2. v1 CLI. 1.18.31 was on PATH pointing at the same data dir, but I cannot prove it executed during that window. It's since been quarantined and opencode now resolves to the bundled 2.2.4 CLI.

   3. Relevant server log lines.

   2026-10-30T20:57:44.373Z level=INFO  cause="SQLiteError: table session_inbox has no column named type"   (×16, 20:57–20:59Z)
   2026-10-30T21:00:15.313Z level=INFO  message="database schema bootstrap started"   migrations=59
   2026-10-30T21:00:15.319Z level=INFO  message="database schema bootstrap completed" migrations=59 durationMs=6
   

   No recovery/backup lines.

   Net: I over-claimed in the original report and I'm narrowing it. Two things I still think are OpenCode-side and worth keeping (happy to split into their own issues if you'd rather):

   • The server logged 16 × table session_inbox has no column named type and only became consistent after a later database schema bootstrap (migrations=59) — i.e. requests touching new columns can be served before the schema is migrated. You also gate /api/info on readiness (server/src/process.ts:192), so a hard readiness gate on migration completion looks like the missing piece.
   • GET /api/info returns {version,pid,urls,paths} with no API/schema generation, which is the same gap as Expose an API version in /api/info + publish a v1→v2 migration path (routes, prompt payload, events, sessions) #55705.

   Want me to retitle this to the schema/readiness issue, or close it in favour of #55010 / #55282 / #55705?
4. carlsuburbmates

   changed the title [-]data: orphaned temp files and large database backups left inside the live data directory[/-] [+]db: server serves before schema migration completes ("table session_inbox has no column named type")[/+] on Oct 30, 2026
5. opencodejr

   closed this as not plannedon Nov 2, 2026
6. opencodejr commented on Nov 2, 2026

   

   opencodejrBot

   on Nov 2, 2026

   Contributor

   More actions

   We're closing this issue as not planned because we haven't heard back.

   OpenCode v2.2.4 has no code that creates .!<pid>!<name> temp files or the opencode.db.corrupted-backup-* / opencode.db.pre-v2migration-backup-* copies. So we need to know which tool, script or process wrote them before we can treat this as an OpenCode bug.

   If you find out, for example from a backup or sync tool, an agent or script that ran a repair, or log lines in ~/.local/share/opencode/log/ that point to OpenCode, please comment with the details and we can reopen this. Thanks for the thorough write-up!