Skip to content

fix(experts): start SQLite when libpq is unavailable - #1934

Merged
jubaoliang merged 1 commit into
developfrom
fix/startup-without-libpq
Oct 12, 2026
Merged

jubaoliang merged 1 commit into
developfrom
fix/startup-without-libpq

Conversation

@jubaoliang

Copy link
Copy Markdown
Collaborator

Summary

  • SQLite startup no longer imports psycopg unconditionally, so Windows ARM64 portable builds (and any host without a loadable libpq) can boot.
  • Publishing an expert still maps a SQLite unique-constraint failure to a taken slug, and still recognizes PostgreSQL IntegrityError when the driver loads.

Test plan

  • uv run pytest tests/unit/agents/test_expert_publish_snapshot.py -q
  • Pre-commit make precommit (format, lint, typecheck, tests) and dashboard build
  • Rebuild the Windows ARM64 portable package and confirm octop starts with the default SQLite database
  • On a host with psycopg / libpq, publish an expert whose slug is already taken and confirm the conflict is still reported

Made with Cursor

Windows ARM64 portable builds omit psycopg-binary, so a top-level psycopg
import crashed startup even when PostgreSQL was not in use.

Co-authored-by: Cursor <cursoragent@cursor.com>
@jubaoliang
jubaoliang merged commit 97f459e into develop Oct 12, 2026
3 checks passed
@jubaoliang
jubaoliang deleted the fix/startup-without-libpq branch October 12, 2026 06:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants