Skip to content

feat: Mark missed files from filesystem as "missing" #1977

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 17 commits into from
Jun 13, 2025
Merged

Conversation

zurdi15
Copy link
Member

@zurdi15 zurdi15 commented Jun 12, 2025

Description
This PR changes the scanner behaviour when any entity (rom, platform or firmware) is missing from the filesystem. Now instead of purging it from the database, will be marked as missing avoiding user data loss. If the file is restored (same path, same filename) and a scan is performed, will be unmarked as missing again.

Checklist

  • I've tested the changes locally
  • I've updated relevant comments
  • I've assigned reviewers for this PR
  • I've added unit tests that cover the changes

Screenshots

image

image

Closes #1784, #1976

Copy link

trunk-io bot commented Jun 12, 2025

Running Code Quality on PRs by uploading data to Trunk will soon be removed. You can still run checks on your PRs using trunk-action - see the migration guide for more information.

@zurdi15 zurdi15 changed the base branch from release to master June 12, 2025 14:43
Copy link

github-actions bot commented Jun 12, 2025

Test Results

92 tests   92 ✅  29s ⏱️
 1 suites   0 💤
 1 files     0 ❌

Results for commit 81f9a10.

♻️ This comment has been updated with latest results.

Copy link
Member

@gantoine gantoine left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thanks for keeping the implementation clean 🫡

@zurdi15 zurdi15 requested a review from gantoine June 12, 2025 23:07
@zurdi15 zurdi15 merged commit c4213ff into master Jun 13, 2025
11 checks passed
@zurdi15 zurdi15 deleted the romm-1784 branch June 13, 2025 06:34
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