release / go (push) Successful in 2m6s
release / web (push) Successful in 1m15s
release / govulncheck (push) Successful in 19s
release / integration (push) Successful in 4m46s
release / android (push) Successful in 4m47s
release / Build signed APK (push) Successful in 5m38s
release / Attach APK to the Release (tag releases only) (push) Skipped
release / Build + push container image (push) Successful in 31s
release / Verify release artifacts (tag releases only) (push) Skipped
Reports, Duplicates and Suspect sources now end the same way: the file
goes and the track stays, marked missing with its likes, plays and
playlist places, until a good copy lands in the library and move
adoption or missing-pair folding brings it back.
- library.RemoveFile removes one track's file and marks the track
missing with the queue it was removed from and who removed it
(tracks.removed_reason / removed_by, migration 0104). The duplicate
resolver's wrong-slot removal shares the same marking.
- POST /api/admin/quarantine/{id}/remove-file removes a reported file,
clears the listeners' reports, marks open playback errors deleted and
records removed_file in the Reports history. A wrong-file or
wrong-tags report drops the file's recording MBID.
- POST /api/admin/library/suspect-sources/{id}/remove removes a video
rip's file and its MBID, and writes a suspect_file_remove audit row.
- The removal reason clears with the missing mark when a file returns.
Grimoire #7743 (milestone 635).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
23 lines
1.2 KiB
SQL
23 lines
1.2 KiB
SQL
-- 0104_removed_tracks.up.sql — a track whose file an admin removed waits for a
|
|
-- good copy, and says why.
|
|
--
|
|
-- Removing a bad file from Reports, Duplicates or Suspect sources keeps the
|
|
-- track: it is marked missing with its likes, plays and playlist places, and
|
|
-- a good copy that lands in the library later is adopted or folded into it.
|
|
-- removed_reason says which queue it was removed from and removed_by who did
|
|
-- it (NULL when the duplicate resolver did it on its own). Both describe the
|
|
-- current missing spell only, so they are cleared with the missing mark, and
|
|
-- the CHECK keeps them off a present track.
|
|
--
|
|
-- removed_file is the Reports history's name for that removal, beside
|
|
-- deleted_file, which removes the track as well.
|
|
ALTER TABLE tracks
|
|
ADD COLUMN removed_reason text,
|
|
ADD COLUMN removed_by uuid REFERENCES users(id) ON DELETE SET NULL,
|
|
ADD CONSTRAINT tracks_removed_reason_check
|
|
CHECK (removed_reason IN ('report', 'duplicate', 'suspect')),
|
|
ADD CONSTRAINT tracks_removed_only_missing
|
|
CHECK (missing_since IS NOT NULL OR (removed_reason IS NULL AND removed_by IS NULL));
|
|
|
|
ALTER TYPE quarantine_action_kind ADD VALUE IF NOT EXISTS 'removed_file';
|