mirror of
https://github.com/navidrome/navidrome.git
synced 2026-10-18 07:30:29 +00:00
835897674b
The artists-first ordering spec asserted the order of a slice literal through an eleven-line mock subclass built only to observe it, and the headstart it guarded barely exists: artists drain in their own pool, so entering the queue first buys them nothing at drain time. The rest were assertions that can no longer discriminate. ReconcileConfigFingerprint holds no queue reference, so asserting it enqueued nothing could not fail. MarkConfigApplied wraps one Property.Put and the reprocess table already covers it end to end. The absent total in the status report is now derived from the source breakdown, so the Sources spec above it asserts the same number by the same path. And both entries of the view-on-absent table hit one branch now that the one-hour threshold is gone; the older one is the guard. Three fingerprint specs asserting one fact about three inputs collapse into a table. Two comments outliving their reason: a fingerprint change no longer re-resolves anything, it reports a stale config.