maziggy b171980688 fix(archives): backfill NULL created_at + tolerate NULL in response (#1732) ...

Older print_archives rows (and rows that landed via the SQLite ↔ Postgres
  cross-DB restore path) can have created_at = NULL because the column was
  originally created without a DEFAULT clause — server_default=func.now()
  only fires at table creation, not for existing rows or raw cross-DB
  inserts. The list_archives response model required a datetime, so a
  single NULL row 500'd the whole endpoint via Pydantic ResponseValidationError.

  - Boot-time backfill: COALESCE(completed_at, started_at, now()) for
    any row where created_at IS NULL. Dialect-branched (SQLite datetime('now')
    vs Postgres NOW()).
  - Schema: created_at is now Optional on ArchiveDuplicate, ArchiveResponse,
    and ArchiveSlim so a future NULL-leaking path doesn't break the list
    endpoint again.

2026-06-14 12:21:57 +02:00

..

app

fix(archives): backfill NULL created_at + tolerate NULL in response (#1732)

2026-06-14 12:21:57 +02:00

tests

fix(vp): Send All enqueues one item per plate; archive delete cascades to queue

2026-06-13 15:58:57 +02:00

__init__.py

…