Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

backup.db.test.js 'restore older database' fails restore_preflight in local pregate DB suite

Open
#12,526 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
57/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
javascript, node.js
Domain
database, testing

Research direction

Start by reproducing the failure on origin/main with a freshly provisioned portos_test database using npm run setup:db:test, then run npm run test:db for services/backup.db.test.js. The issue leaves open whether the cause is stale local database state or the preflight/test fixture, so compare those runs before changing anything. Done when the test passes on a freshly provisioned database.

Written by the indexing model from the issue text.

Description

effort:small model:medium

Observed during local npm run pregate DB suite (portos_test) while working on #12492 (change does not touch backup).

Actual: services/backup.db.test.js > restore older database fails: restore_preflight Database contains unexpected objects, ownership, or dependencies. Restore was refused without changing data. (expected 'ok', got 'failed').

Unconfirmed whether this reproduces on a clean main or is specific to the local portos_test database state.

Next step: reproduce on origin/main with a freshly provisioned portos_test (npm run setup:db:test); if it reproduces, fix the preflight/test fixture; if only stale local state, make the test provision or reset what it needs.

Acceptance: npm run test:db passes backup.db.test.js on a freshly provisioned portos_test.

Dominant language
JavaScript
Stars
38
Forks
32
Avg merge
31m
Merged PRs (30d)
995

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from atomantic/PortOS

All issues in atomantic/PortOS

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.