|
Some checks failed
CI / Lint, typecheck, test (pull_request) Successful in 6m48s
CI / Build container images (pull_request) Successful in 1m46s
CI / Auth e2e pack (pull_request) Successful in 8m22s
CI / Import/export fidelity gate (pull_request) Successful in 1m8s
CD / Deploy to Test (push) Blocked by required conditions
CD / Smoke tests against Test (push) Blocked by required conditions
CD / Promote to Int (push) Blocked by required conditions
CI / Auth e2e pack (push) Blocked by required conditions
CI / Import/export fidelity gate (push) Blocked by required conditions
CI / Build container images (push) Blocked by required conditions
CD / Build and push images (push) Has been cancelled
CI / Lint, typecheck, test (push) Has been cancelled
Since #224 read_events is partitioned; the dump carries per-partition primary keys as own entries, and pg_restore --clean emitted DROP CONSTRAINT against inherited constraints, which PostgreSQL refuses. The restore then reported FAILED although the content was restored. Dropping and recreating the public schema first makes every --clean drop a no-op and the restore faithful: objects created after the backup no longer survive. Verified in the isolated environment of #220 (set 20260731-132200, exit 0, readyz green). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01AUtYMxwTCMHG9mVHnwbFg8 |
||
|---|---|---|
| .. | ||
| archive.test.ts | ||
| archive.ts | ||
| backup-set.test.ts | ||
| backup-set.ts | ||
| commands.ts | ||
| config.test.ts | ||
| config.ts | ||
| index.ts | ||
| mail.test.ts | ||
| mail.ts | ||
| mirror.test.ts | ||
| mirror.ts | ||
| perform-restore.ts | ||
| pg.test.ts | ||
| pg.ts | ||
| remote.test.ts | ||
| remote.ts | ||
| restore-orchestrator.test.ts | ||
| restore-orchestrator.ts | ||
| restore.ts | ||
| runner.test.ts | ||
| runner.ts | ||
| scheduler.test.ts | ||
| scheduler.ts | ||
| settings.test.ts | ||
| settings.ts | ||
| status.ts | ||