Database schema issue on the backend (sync_behavior column missing) preventing Space creation #143

Activity

1. rbuergi

   added a commit that references this issue on Jul 1, 2026

   Merge pull request #144 from Systemorph/fix/stable-assemblyversion-143

   ...

   4779b4e
2. rbuergi

   closed this as completedin #144on Jul 1, 2026
3. rbuergi commented on Oct 11, 2026

   

   rbuergi

   on Oct 11, 2026

   Contributor

   More actions

   (re-posted 2026-10-11; originally by @rbuergi on 2026-07-01)

   Root cause found (2026-07-01). The sync_behavior column is missing because the database migration never runs — the memex-migration container on the current image (3.0.0-ci.122 / 6943991) crashes on startup:

   Current DB version: 39
   Unhandled exception. System.IO.FileNotFoundException: Could not load file or assembly
   'MeshWeaver.Documentation, Version=3.0.0.280, Culture=neutral, PublicKeyToken=null'.
   

   So the memex-migration-deployment is in CrashLoopBackOff on client-i + memex (verified), the schema stays at v39, and the migration that adds sync_behavior (PR #119, MeshNode.SyncBehavior persistence) is never applied → Space creation fails exactly as reported.

   Note this is separate from the portal: the portals on ci.122 run fine (all 3 rolled and 1/1 Running) — only the migration image is broken. It's a packaging/assembly-version mismatch: the migration binary references MeshWeaver.Documentation v3.0.0.280 but that assembly isn't present at that version in the migration image.

   Fix required: correct the memex-migration image build so MeshWeaver.Documentation is packaged at the referenced version (CD build), then let the migration run to apply v40 (sync_behavior). Until then the schema can't advance past v39. Investigating the migration image build next.