backup.db.test restore older database schema fails in local pregate DB suite
Maintainers usually reply within 1 day
@atomantic is already working on this.
Since Oct 19, 2026.
Assessment
This issue has not been assessed yet.
Description
Observed during npm run pregate on a branch that touches only videoGen files (PR #12305): the serial DB suite (npm run test:db:ci --prefix server) failed at server/services/backup.db.test.js > "restore older database schema" > "restores a real pre-FK dump, discards newer rows, and runs schema upgrades" (line 173): restore() resolved { status: 'failed' } where { status: 'ok', dryRun: false } was expected. All other pregate stages were green; migrations 007 applied before the failure.
Not yet determined whether this is local-environment (e.g. pg_restore/psql version on the dev machine) or a real regression on main.
Next step: rerun npm run test:db on current main locally and print the restore() failure reason; fix the cause or make the test surface it.
Acceptance: the test passes locally and in CI, and a failed restore reports its reason in the assertion output.
- Dominant language
- JavaScript
- Stars
- 38
- Forks
- 32
- Avg merge
- 31m
- Merged PRs (30d)
- 995
Getting set up
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from atomantic/PortOS
-
effort:medium model:medium plan planner:opus-5-5 security
Difficulty 3/5 1-2 days Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
effort:small model:medium
Difficulty 3/5 1-2 days Newbie friendliness 57/100
atomantic/PortOS#12526 · 1 comment ·
Maintainers usually reply within 1 day
-
bug effort:high model:heavy plan
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Maintainers usually reply within 1 day
-
bug effort:medium model:medium plan
Difficulty 3/5 1-2 days Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
area:federation bug data-integrity effort:medium model:heavy plan
Difficulty 4/5 1-2 days Newbie friendliness 48/100
Maintainers usually reply within 1 day
All issues in atomantic/PortOS
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
subhranshudash13-dotcom/Contribo#74 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 67/100
ThatGuySam/doesitarm#1114 ·
-
enhancement good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
laaielichter/Reverseport#44 ·
Maintainers usually reply within 1 day
-
failed for an unknown reason
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
OpenTermsArchive/contrib-declarations#4148 ·
Maintainers usually reply within 1 day