andrew
59c369c9e2
Playlist detail page's status section (and the new two-column compare view) was never rendering: the router awaited status_service.playlist_status(), but that function is plain sync, so awaiting its dict return raised "object dict can't be used in 'await' expression" on every load, silently caught and shown as a generic fetch error. Removed the erroneous await. find-fuzzy-dupes.py's --apply and --apply-pairs both deleted by a `path::` regex query even though the beets id was already available in scope -- same mixed-path-storage issue (pre/post beets-2.11-upgrade items store absolute vs. library-relative paths) dedup-library.sh already worked around by deleting via id instead. This silently failed to match for most confirmed fuzzy-audio deletions (verified: 19 of 20 in one run). Added a delete_id column to dedup_candidates, threaded through the scan/apply pipeline, and switched both delete call sites to `id:`. Dedup scans also never checked whether a pair was already sitting in the pending list, so every re-scan (including the daily schedule) added a new row for the same unreviewed duplicate -- cleaned up 38 redundant rows already in production and added a check so future scans skip a pair that's already pending. Dashboard gets a Public IP stat card (cached 10 min, fetched via ipify) as a quick confidence check that outbound traffic is actually routed through gluetun's VPN and not the home connection.
11 lines
593 B
SQL
11 lines
593 B
SQL
-- Stores the beets item id of the delete_path side of a fuzzy_audio
|
|
-- candidate. find-fuzzy-dupes.py was deleting by `path::` query, which
|
|
-- silently fails to match a large fraction of the library (mixed absolute
|
|
-- vs. library-relative path storage left over from the beets 2.11
|
|
-- upgrade -- the same issue dedup-library.sh already works around by
|
|
-- deleting via `id:` instead). Nullable: existing pending candidates
|
|
-- scanned before this column existed fall back to the old path query.
|
|
ALTER TABLE dedup_candidates ADD COLUMN delete_id INTEGER;
|
|
|
|
UPDATE schema_version SET version = 3;
|