gabriel / musehub public
fix fix/is-ancestor-db-parent-ids #1 / 1
gabriel · 72 days ago · Apr 10, 2026 · Diff

fix: _is_ancestor_db uses parent_ids JSON list instead of non-existent parent_commit_id/parent2_commit_id columns

MusehubCommit ORM uses parent_ids: Mapped[list[str]] (JSON list) for parent commit references. _is_ancestor_db() was selecting non-existent column attributes parent_commit_id and parent2_commit_id, causing AttributeError (HTTP 500) during push fast-forward validation when all commits are already present on the remote.

Fix: select parent_ids and iterate row.parent_ids instead of the two-column tuple pattern.

sha256:1e4098c3e912226439a861bcffabed37753f434eae70c2cc2b2b939e4ef02f5b sha
sha256:01b6e4fdecaebc437111316a9bc28a2faa91c27ec35bb6966fa8bb61350f0ab2 parent
sha256:e595bafa73370b43a99bd98e081b64b8ae0c71d89c8e2d239b4631f2f3353e85 snapshot
← Older Oldest on fix/is-ancestor-db-parent-ids
All commits
Newer → Latest on fix/is-ancestor-db-parent-ids

0 comments

No comments yet. Be the first to start the discussion.

To add a comment, use the Muse CLI: muse hub commit comment sha256:1e4098c3e912226439a861bcffabed37753f434eae70c2cc2b2b939e4ef02f5b --body "your comment"