Environment
What happened
After upgrading to v0.18.2, gbrain doctor reports 10 unacknowledged sync failures:
[WARN] sync_failures: 10 unacknowledged sync failure(s).
second-brain/business-consulting/wiki/index.md (column "source_id" does not exist)
second-brain/business-consulting/wiki/log.md (column "source_id" does not exist)
second-brain/business-consulting/wiki/sources/how-to-build-your-second-brain.md (column "source_id" does not exist)
... and 7 more
Root cause
Schema is at version 10. The source_id column doesn't exist at that version — it's added in a later migration. Because the migration chain is wedged at v0.13.0 (see #373), the schema can't advance, and any sync touching the new column fails.
Expected behavior
Either:
- Sync should degrade gracefully when a column is missing (skip the column, don't fail the file), or
- The migration wedge should be surfaced more clearly as the reason for sync failures
Workaround
None until #373 is resolved. Running gbrain sync --skip-failed acknowledges but doesn't fix.
Related
Environment
What happened
After upgrading to v0.18.2,
gbrain doctorreports 10 unacknowledged sync failures:Root cause
Schema is at version 10. The
source_idcolumn doesn't exist at that version — it's added in a later migration. Because the migration chain is wedged at v0.13.0 (see #373), the schema can't advance, and any sync touching the new column fails.Expected behavior
Either:
Workaround
None until #373 is resolved. Running
gbrain sync --skip-failedacknowledges but doesn't fix.Related