8 Commits

Author	SHA1	Message	Date
Psychotoxical	7c724a642f	chore(eslint): add ESLint toolchain and clean src to strict 0/0 (#1165) ... * chore(eslint): add eslint toolchain and configs * fix(eslint): resolve gradual-config errors (rules-of-hooks, no-empty, prefer-const, …) * chore(eslint): clear unused vars in config, contexts, app and test * chore(eslint): clear unused vars in api and music-network * chore(eslint): clear unused vars in utils * chore(eslint): clear unused vars in store * chore(eslint): clear unused vars in cover and hooks * chore(eslint): clear unused vars in components * chore(eslint): clear unused vars in pages * chore(eslint): remove explicit any in src * chore(eslint): align react-hooks exhaustive-deps * chore(eslint): zero gradual config on src * chore(eslint): strict hook rules in store and utils * chore(eslint): strict hook rules in hooks and cover * chore(eslint): strict hook rules in components * chore(eslint): strict hook rules in pages and contexts * chore(eslint): document scripts ignore in eslint config * chore(eslint): add lint script and zero strict findings * chore(eslint): address review round 1 (gradual 0/0, per-site disable reasons) * chore(eslint): tighten two set-state disable comments (review round 2 LOW) * chore(nix): sync npmDepsHash with package-lock.json * docs(changelog): add Under the Hood entry for ESLint setup (PR #1165) --------- Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>	2026-06-24 01:33:34 +02:00
Frank Stellmacher	9fa086c428	feat(server): dual server address (LAN + public) per profile (#880) ... * feat(server): ServerProfile.alternateUrl + shareUsesLocalUrl Additive optional fields on ServerProfile to back the dual-address work. 'alternateUrl' is the optional second endpoint (e.g. LAN counterpart of a public 'url' or vice versa); 'shareUsesLocalUrl' chooses which of the two goes into Orbit / entity / magic-string shares when both are set. Pure schema change — no runtime consumers yet. Single-address profiles keep the same persisted shape; the optional fields are simply absent. * feat(server): serverEndpoint module with LAN classification + IPv6 Introduces a single home for connect-/share-layer URL utilities that the dual-address work will build on: * normalizeServerBaseUrl(raw) — aligned with serverProfileBaseUrl * isLanUrl(url) — IPv4 (unchanged) + IPv6: ::1 loopback, fe80::/10 link-local, fc00::/7 ULA, and IPv4-mapped (both dot-decimal and the URL-API-normalized hex form, since new URL() rewrites ::ffff:1.2.3.4 to ::ffff:HHHH:HHHH) * allNormalizedAddresses(profile) — deduped [url, alternateUrl?] * serverAddressEndpoints(profile) — LAN-first ServerEndpoint[] isLanUrl moves out of useConnectionStatus.ts (the hook now imports + re-exports it for backward compatibility); OrbitStartModal points at the new path directly. 38 unit tests cover the IPv4/IPv6 matrix, dedupe, ordering, and edge cases. * feat(server): pickReachableBaseUrl with in-memory connect cache Adds the runtime connect layer on top of serverEndpoint: * pickReachableBaseUrl(profile) — sequential LAN-first ping via the existing pingWithCredentials; first OK wins. * ensureConnectUrlResolved(profile) — boot / switch / online-event entry point (same mechanism, intent-named). * In-memory cache keyed by profileId; sticky behaviour tries the cached endpoint first, falls back to the natural order on miss. * invalidateReachableEndpointCache(profileId?) — single-profile and whole-cache flushes for profile-edit / credentials-change / online. * getCachedConnectBaseUrl(profileId) — sync getter for getBaseUrl fallback path (next commit). The cache is **session-only**, never persisted. Single-address profiles keep the same shape (one endpoint, one ping). 9 new unit tests cover single + dual address, LAN-first preference, fallthrough, unreachable + stale-cache clear, sticky hit, and the two invalidate flavours. * feat(server): getBaseUrl reads connect cache, falls back to primary url Dual-address profiles need 'getBaseUrl' to return the runtime-probed connect URL (LAN at home, public elsewhere), not the literal primary 'url'. To keep the sync getter shape that ~60 call sites depend on, the store now reads 'getCachedConnectBaseUrl(server.id)' from the serverEndpoint cache. If no probe has run yet (very early boot, before switchActiveServer populates the cache), it falls back to the normalized primary URL — identical to today's behaviour. Single-address profiles see no difference; their cache entry equals serverProfileBaseUrl(url). * feat(server): switch + connection-status probe via ensureConnectUrlResolved Both surfaces that previously called pingWithCredentials(server.url, ...) directly now route through the dual-address connect layer: * switchActiveServer awaits ensureConnectUrlResolved(server), reads the identity (type/serverVersion/openSubsonic) off the returned ping, and hands probe.baseUrl (not server.url) to scheduleInstantMixProbeForServer so the AudioMuse probe also hits the reachable endpoint. * useConnectionStatus.check() does the same on every 120 s tick — sticky cache fast-paths the steady state, and a network change naturally flips the active endpoint without a manual retry. * useConnectionStatus.retry() and the 'online' event flush the cached entry for the active profile first, so the next probe starts from the natural LAN-first order instead of revalidating a stale URL. Single-address profiles behave identically: one endpoint in the list, one ping per check. No behaviour change for them. * feat(server): PickReachableResult.ping + connectBaseUrlForServer helper Two additive extensions to the serverEndpoint surface that the upcoming CONNECT migrations all need: * 'ping: PingWithCredentialsResult' on the OK branch of PickReachableResult so callers (switchActiveServer, useConnectionStatus) can read type/serverVersion/openSubsonic from the same probe instead of issuing a second pingWithCredentials. * connectBaseUrlForServer(server) — sync getter for the connect URL of *any* saved profile (active or not). Reads the cache, falls back to normalized primary url on miss. Becomes the canonical helper for non-active-server HTTP traffic (apiForServer, stream URLs, cover fetches, library bind session). Tests: pingOk() fixture now returns identity fields; the single toEqual-asserting test in pickReachableBaseUrl became a guarded read to keep equality concise while still asserting on the new ping field. * feat(connect): apiForServer + stream URLs route via connectBaseUrlForServer Non-active-server HTTP traffic (the apiForServer entry point, used by QueuePanel cross-server cover fetches and share-paste resolution) and the stream-URL builders previously read 'server.url' directly, bypassing the dual-address connect cache. Both now go through connectBaseUrlForServer, which serves the cached LAN/public endpoint when one exists and falls back to the normalized primary url otherwise. buildStreamUrl(id) now uses the baseUrl it already pulled from getBaseUrl() (which is connect-cache aware as of 2a6d8283) instead of re-normalizing server.url — same value for single-address profiles, correctly dual-address for the rest. Single-address callers see no behaviour change. * feat(connect): cover fetch + cover-cache ensure use connect URL Both cover-fetch surfaces previously read 'scope.url' / 'server.url' straight into HTTP requests, which would freeze the cover pipeline on the primary URL even when a LAN endpoint was reachable: * buildCoverArtFetchUrl(ref, tier) — for the 'server' scope (queue rows cached against a non-active profile) and the 'playback' scope (cross-server playback) now resolves the connect URL via connectBaseUrlForServer before handing off to buildCoverArtUrlForServer. * ensureArgsFromRef in coverCache.ts — restBaseUrl for the Tauri 'cover_cache_ensure' invoke now uses the cached connect URL for both 'server' and 'active'/'playback' scopes. Scope.url itself remains the index-stable primary URL — that's what storageKeys (INDEX) consume. Only the HTTP base shifts to the connect endpoint, exactly the split the spec calls out. * feat(connect): library bind + server-test probe via ensureConnectUrlResolved Two more 'rebind / re-test an existing saved server' paths still pinged the literal primary URL — both go through the dual-address connect layer now: * bindIndexedServer (librarySession.ts): used to ping server.url then pass serverProfileBaseUrl(server) as the bind 'baseUrl' to Rust. Now: one ensureConnectUrlResolved call covers both — probe.baseUrl feeds librarySyncBindSession directly, so Rust's per-server library sync uses whichever endpoint actually answered. Drops the pingWithCredentials and serverProfileBaseUrl imports. * testConnection (ServersTab.tsx): same shape — probe via the connect layer, read identity from probe.ping, hand probe.baseUrl to scheduleInstantMixProbeForServer so the AudioMuse probe also hits the connect endpoint. Single-address profiles still ping once. Add/edit save handlers (handleAddServer / handleEditServer) keep the direct pingWithCredentials against the user-entered data.url — that flow is the dual-address verify hook, which PR 2 extends. * feat(server): serverShareBaseUrl — public-by-default share URL picker Adds the share-layer companion to connectBaseUrlForServer. Different intent: connect picks the reachable endpoint for HTTP, share picks the URL that goes into Orbit invites / entity share payloads / queue share links / magic strings — where a guest opening the link is not on the host's LAN. Logic per spec §5.1: * Single-address profile → that one address (normalized). * Both set, default flag → public. * Both set, shareUsesLocalUrl flag → local. * Edge cases (both LAN, both public, missing one of the two): fall back to the first endpoint in the list so the function is total. Empty profile returns the normalized url (possibly empty) — defensive, never throws. 7 unit tests pin all six branches plus the empty case. Call-site migration (Orbit, copyEntityShareLink, QueuePanel, magic string srv field, findServerIdForShareUrl, Orbit LAN warning) lands in the next commits. * feat(share): Orbit + entity + queue shares use serverShareBaseUrl Four share-encoding surfaces previously read 'getBaseUrl()' (connect) or the raw 'server.url' (primary) when embedding the host into outgoing share links — both wrong for a dual-address profile: * copyEntityShareLink (track / album / artist / composer) — was getBaseUrl(); now reads serverShareBaseUrl(active). Guests opening the link are off-LAN, so public is the right default. * OrbitStartModal — was raw server?.url for both 'buildOrbitShareLink' and the LAN warning. Now goes through serverShareBaseUrl; the LAN warning correspondingly reflects the address the guest will see, not the host's primary. * OrbitSharePopover — same fix on the host-only share popover. * QueuePanel.handleCopyQueueShare — was getBaseUrl(); same migration. Single-address profiles return exactly the same string from serverShareBaseUrl as serverProfileBaseUrl(server.url) did before, so no behaviour change for the common case. shareUsesLocalUrl flips the default to LAN for the rare 'share into a LAN-only group' use; that checkbox lands with the form UI in the next sub-phase. findServerIdForShareUrl + paste-side share matchers are migrated in the next commit (read-side of the same contract). * feat(share): paste-side resolves dual-address profiles + connect URL Read-side counterpart to the encode-side migration: * findServerIdForShareUrl(servers, shareSrv) now matches a profile when shareSrv normalizes to either profile.url OR profile.alternateUrl. Without this, a paste of a link generated against the host's LAN address (shareUsesLocalUrl=true) would fail to find the local saved profile even though it's the same server. * resolveSharedSong / resolveShareSearchAlbum / resolveShareSearchArtist in enqueueShareSearchPayload now hand connectBaseUrlForServer(lookup.server) to the *WithCredentials HTTP calls instead of the raw lookup.server.url. The looked-up profile may be dual-address; this routes the song / album / artist fetch through whichever endpoint is currently reachable. Indirect consumers (shareServerOriginLabel, shareQueueServerContext) read the same findServerIdForShareUrl, so no code change needed there — they now match both addresses transparently. * feat(verify): serverFingerprint + same-server verification Pure-logic core of dual-address verify. Three exports: * fetchServerFingerprint(baseUrl, user, pass) — one ping (envelope 'version' extracted alongside type/serverVersion/openSubsonic) plus four soft-fail optional calls in parallel (getMusicFolders, getUser, getLicense, getIndexes). Optional failures collapse to null fields, not whole-fingerprint failure. Subsonic-generic — never branches on type === 'navidrome'. indexesDigest is a hash of letter-count plus sorted first 20 artist ids, so two probes against the same library see the same digest without comparing full payloads. * compareFingerprints(a, b) — strict on the ping triple (type case-insensitive, serverVersion exact, openSubsonic boolean); envelope apiVersion informational only. Body signals counted only when both sides have a non-null value; empty musicFolders [] on both sides still counts as a matching signal. Result: 'match' (>=1 common signal all agreeing) / 'mismatch' (any common differs) / 'insufficient' (0 common). No 'save anyway' for insufficient in v1. * verifySameServerEndpoints(profile, user, pass) — single-address short-circuits to ok:true (nothing to verify). Otherwise parallel fingerprint probes, then pairwise compare. Ping-fail on any endpoint reports the offending host for the UI. 20 unit tests cover the compare matrix (every body signal in every direction), Navidrome- vs minimal-Subsonic-shape probes, ping-fail, and all four verify outcomes (ok / unreachable / mismatch / insufficient). HTTP mocked via vi.stubGlobal('fetch') + plain-object Response shape (avoiding any Response-polyfill dependency). * feat(boundary): resolve_host_addresses Tauri command + TS wrapper Adds one additive invoke for dual-address form hints. Spec §9.1 + contracts.md §6. Rust side (src-tauri/src/lib_commands/app_api/network.rs): * #[tauri::command] resolve_host_addresses(hostname: String) -> Result<Vec<String>, String> * tokio::net::lookup_host with a port suffix (':0'); discards the port from each SocketAddr, dedupes addresses via HashSet. * strip_port helper handles 'host:port', 'ipv4:port', '[ipv6]:port', '[ipv6]' (no port), and bare 'ipv6' (left as-is for lookup_host to wrap). 7 unit tests cover each shape. * Lookup failure → Ok(vec![]) so a DNS hiccup doesn't surface as an error toast or block the save flow — form-hint only. Frontend wrapper (src/api/network.ts): * resolveHostAddresses(hostname) — trims, invokes, swallows errors to an empty array so consumers get a clean total function. §04 boundary note: additive command, no breaking change. Added to the invoke_handler! generate_handler list in lib.rs at the natural alphabetical-ish slot near migration_run. * feat(form): AddServerForm — second optional address + share flag + DNS hint UI side of dual-address. AddServerForm now carries the four new moving parts spec §6 calls out: * Second address field ('Second address (optional)') under the primary URL. Placeholder flips to suggest the opposite kind of address based on the primary's LAN classification. * Contextual hint under the second field when it's empty — 'add a public address for outside-home use' (primary is LAN) or 'add a local address for faster home access' (primary is public). Hint disappears once the field has content. * Two-LAN client-side check on submit: when both addresses classify as LAN, save is blocked with a toast. Reverse case (both public) intentionally allowed per spec §6.3. * shareUsesLocalUrl checkbox — visibility rule per spec §5.3: hidden until the second address has content; shows with the persisted value on edit; cleared when the user empties the second address before save. DNS hint: on primary-URL blur we call the Tauri resolve_host_addresses command and classify the response by isLanUrl. Literal IPs skip DNS (already classified locally). DNS miss → no hint surfaces (never blocks save). Used only for the hint text — connect still goes through pingWithCredentials. i18n: 9 new keys in en + ru (serverAlternateUrl*, shareUsesLocalUrl*, serverBothLanError). Other locales fall back to English. onSave signature widened to 'void | Promise<void>' — ServersTab / Login both accept that already. The save flow itself still calls the legacy pingWithCredentials path; verify wiring lands in 2e. * feat(verify): wire verifySameServerEndpoints into add + dual-edit flows Save flow now blocks persisting a dual-address profile that fails the same-server check. Spec §6.4 + §7.4. handleAddServer: * When data.alternateUrl is non-empty, runs verifySameServerEndpoints BEFORE the existing ping. mismatch / insufficient / unreachable each surface a localized toast and abort the save (no addServer call). * Single-address adds keep the legacy single-ping path — no extra network round-trip when there's nothing to verify. handleEditServer: * Unconditional save remains the default — but if the edit either introduces / changes alternateUrl OR changes url / username / password while alternateUrl is set, verify runs first and may block. * After persist, invalidates the reachable-endpoint cache for this profile id so any sticky cached connect URL from before the edit is re-probed on the next access (credentials may have changed, alternate may have appeared). i18n: 4 new toast keys in en + ru (dualAddressVerifying placeholder for future progress UI, plus mismatch / insufficient / unreachable). Other locales fall back to English. announceVerifyResult helper keeps the toast routing in one place so handleAddServer and handleEditServer share the same surface. * i18n(settings): dual-address keys across all 9 locales Adds the 13 new dual-address keys to the remaining 7 locales: de · fr · es · nl · nb · ro · zh. * serverAlternateUrl + placeholderPublic / placeholderLocal * serverAlternateUrlHintAddPublic / HintAddLocal (contextual hints under the second-address field) * serverBothLanError (client-side two-LAN validation) * dualAddressVerifying / Mismatch / Insufficient / Unreachable (toast strings; Unreachable carries the {{host}} interpolation) * shareUsesLocalUrl + Desc (checkbox label + short description) Placeholders (example.com URL / 192.168.1.100:4533) kept identical across all locales — same shape the existing serverUrlPlaceholder already uses. Single coordinated sweep so every supported language ships dual- address fully translated rather than falling back to English. * feat(cover): cover_cache_rename_server_bucket Tauri command Adds the disk-side companion to the upcoming URL-change remigration flow (dual-server-address spec §8.3). When a user edits the primary url so the derived index key changes, the SQLite migration already re-tags rows via the existing migration_run command — this command moves the cover-cache bucket on disk so cached WebP tiles stay reachable under the new key. Behaviour: * old_key == new_key → no-op. * Old bucket missing → no-op success (nothing to migrate). * New bucket missing → simple fs::rename (fastest path). * Both exist → recursive merge with 'prefer existing' on file collision (the newer bucket wins; data is never lost). * Emits 'cover:bucket-renamed' with {oldKey, newKey} on success so the frontend disk-src cache can invalidate stale URLs. Sanitization: rejects empty, backslash, and '..' path segments at the FS boundary. Forward slashes are legitimate (a Navidrome mounted at a subpath like 'music.example.com/navidrome' produces an index key with one); they're handled by Path::join. 4 unit tests cover key sanitization (accepts real keys, rejects traversal/backslash) and the merge semantics (unique-file move + prefer-existing on collision). Registered in lib.rs invoke handler. * feat(remap): rewriteFrontendStoreKeysForRemap — explicit oldKey→newKey path Adds the URL-change remigration entry point next to the existing UUID→indexKey migration. Same plumbing (offline store, hot cache, analysis-strategy maps) but driven by explicit { oldKey, newKey }[] mappings instead of being derived from the current servers list. Also folds in the player-side cleanup the existing path didn't have: * queueServerId — if currently bound to a remapped index key, repoint to the new one so playback continues through the rename instead of looking unbound. * analysisStrategyStore — runs the same map-key swap inline (the 'migrateServerOverrides' helper handles UUID→indexKey, not indexKey→indexKey). Same prefer-existing-on-collision semantics as the disk-side cover_cache_rename_server_bucket — if a destination key already carries data, we keep it. 8 unit tests cover no-ops, the four store rewrites, the queue repoint, the 'leave other servers untouched' guarantee, and the collision case. * feat(remap): serverUrlRemigration orchestrator — 4-stage pipeline Single-file orchestrator that runs the full URL-change remigration when a profile edit shifts the primary url's derived index key. Spec §8 + contracts.md §4. Two exports: * indexKeyRemapForUrlChange(prev, next): IndexKeyRemap | null — short-circuits scheme-only edits ('http://x' ↔ 'https://x'), trailing-slash differences, and alternateUrl-only changes by normalizing both sides through serverIndexKeyFromUrl and returning null when they match. Empty urls also return null. * runIndexKeyRemigration(remap): Promise<IndexKeyRemigrationResult> — runs inspect → run → frontend-rewrite → cover-rename in order, aborts on the first failure and reports the offending stage. Failure ordering rationale: * inspect / run failures stop the destructive step — DB is untouched, the caller can retry safely. * frontend rewrite swallows errors (best-effort; zustand persist catches up on rehydrate next session). * cover-rename failure is reported but does NOT roll back the DB rows (that would be even more destructive); covers under the old key recover via the existing cover backfill on next access. 10 tests cover the detect logic (5 cases including the path-suffix case) plus all four pipeline stages with mocked Tauri invoke — including verifying the legacyId/indexKey mapping shape lands on both inspect and run calls. * feat(remap): wire URL-change remigration into ServersTab edit flow handleEditServer now detects a primary-url index-key change BEFORE any other save logic (verify, persist, etc.) and orchestrates the full remigration when one is needed. Flow: * indexKeyRemapForUrlChange(prev, next) — null for scheme-only edits / alternateUrl-only edits / no-op edits, so the common case falls straight through without prompting the user. * On a real remap → confirm modal via useConfirmModalStore.request (danger style, plain-language oldKey → newKey copy, explicit 'cannot be undone'). User cancel → abort save entirely. * On confirm → runIndexKeyRemigration pipeline. Failure surfaces a stage-specific toast (inspect / run / cover-rename — wording per spec §8.4 + the recoverability matrix in serverUrlRemigration.ts). * On success → fall through to the existing dual-address verify, then auth.updateServer + invalidate cache + ping (unchanged). i18n: 7 new keys (urlRemigrationTitle / Message with oldKey + newKey interpolation / Confirm / Progress / FailureInspect / FailureRun / FailureCoverRename) — full sweep across all 9 locales (en, de, ru, fr, es, nl, nb, ro, zh). Test fixup: the offline-store collision test in rewriteFrontendStoreKeys needed an 'as unknown as' cast — the existing OfflineTrackMeta type doesn't carry the test-only marker property, and a one-step cast TS rejected as not overlapping enough. * feat(magic): magic-string v2 encode/decode with dual-address fields Adds the v2 wire format for server invites. Spec §10 + contracts.md §5.2. Encode is opportunistic: payloads with alternateUrl set OR shareUsesLocalUrl=true emit v2; everything else stays v1 byte-identical. This means single-address profiles keep producing exactly the same invite they did before — older receivers can't tell the difference. v2 shape: { v: 2, url, alt?, shareLocal?, u, w, n? } * url — the host's share URL (public by default; LAN if shareLocal), NOT necessarily the host's primary URL. Receiver treats it as the primary of the new profile (their own index key). * alt — the host's alternate address (the other half of the pair). * shareLocal — mirrors the host's shareUsesLocalUrl preference so onward shares from the receiver behave the same way. Decode accepts both v1 and v2. v2-only fields are left undefined when decoding a v1 payload (no '|| undefined' shim — kept absent so zustand persist diffs stay clean). Defensive: an empty alt on a v2 invite decodes as if the field were absent, never as ''. Test updates: 'rejects a payload with the wrong version' now targets v: 3 (v: 2 became valid). 7 new tests cover the v1/v2 wire-format choice, both v2 round-trip shapes, the v1-decode-into-v2-fields- undefined backward-compat case, and the empty-alt edge. * feat(magic): wire magic-string v2 through invite-encode + paste consumers Five surfaces now produce / accept v2 invites with the dual-address fields end-to-end: Encode side (admin → user invite): * MagicStringModal — looks up the saved profile that matches the serverUrl prop (primary OR alternateUrl normalize-match) and encodes through serverShareBaseUrl + alternateUrl + the share flag. Falls back to plain v1 for single-address profiles. * UserForm — same lookup + encode plumbing on the in-form 'Save & get magic string' flow. Decode side (paste invite into form): * AddServerForm useEffect (initialInvite from outer state) + handleMagicStringChange (live paste) both pull alternateUrl and shareUsesLocalUrl off the decoded payload into form state, so the second-address field + checkbox surface immediately on a v2 paste. * Login form state gains hidden alternateUrl + shareUsesLocalUrl fields (not user-editable — Login stays single-address by design); v2 paste / initial-invite both populate them so they persist with the new profile via addServer. handleQuickConnect likewise forwards the existing dual-address shape for already-saved profiles. * attemptConnect signature widened with the two optional fields; addServer / updateServer call sites conditionally include them only when alternateUrl is non-empty so single-address profiles keep their lean persisted shape. Both encode helpers share the same magicPayloadAddressFields lookup (MagicStringModal + UserForm) — the duplication is acceptable for two co-located small files but a single shared helper would be the natural place to consolidate if a third encoder appears. * fix(form): magic-string submit forwards decoded alternateUrl + share flag AddServerForm.submit's magic-string branch was forwarding only name/url/username/password from the decoded payload, silently dropping alternateUrl + shareUsesLocalUrl. A v2 invite pasted into the magic-string field and saved would land in the store as a single- address profile even though handleMagicStringChange had already populated the dual-address fields into form state for display. Now the magic branch picks the dual-address fields off the decoded payload (same conditional spread as the non-magic branch a few lines down) so v2 invites round-trip end-to-end through the form. * fix(verify): extractUserId drops username fallback to avoid false mismatches Spec §7.2 footnote: 'fallback (normalized username) only if no id on either side'. The old extract unconditionally fell back to the authenticated username whenever user.id was empty — but the comparator can't tell username-fallback apart from a server-supplied id. So a server pair where endpoint A returns user.id='42' and endpoint B only returns user.username='frank' would land in compare with userId values '42' vs 'frank' and report mismatch on what is actually the same user on the same server. Now extractUserId returns null when user.id is absent. Both sides returning null means compareFingerprints skips userId as a common signal (correct behaviour per the §7.3 'both sides have a value' rule). One new test pins it; the call site drops the redundant fallbackUsername argument. * fix(remap): rewriteFrontendStoreKeysForRemap migrates coverStrategyStore Spec §8.2 lists 'analysis/cover strategy maps' as targets of the URL-change remigration. The For-Remap path covered analysis but missed cover — a user-set cover strategy override (e.g. 'aggressive' for one server) would silently drop when the user edited that profile's primary URL, because the key tagged under the old index key never made it to the new one. Same shape as the analysis remap inline: prefer-existing on collision (newer key wins), delete the legacy entry afterwards. One new test pins the move; setup adds a fresh useCoverStrategyStore reset between cases. * fix(cover): is_safe_index_key rejects absolute paths + drive letters Defense-in-depth gap in cover_cache_rename_server_bucket. The old sanitizer only rejected backslashes and '..' segments — '/etc/passwd' on Unix and 'C:\Windows' on Windows both passed. Path::join with an absolute argument REPLACES the base path, so root.join('/etc/passwd') on Unix would walk out of cover-cache entirely. Real index keys never reach this state — they come out of serverIndexKeyFromUrl which strips schemes and trailing slashes, so no leading separator and no drive-letter prefix is ever produced. But the comment promises 'defense in depth' and that defense is worth completing. Now rejects: * empty keys (would join to the cover-cache root itself) * leading '/' or '\' * Windows drive-letter prefix 'X:' (case-insensitive ASCII letter) * backslashes anywhere (separators are forward-slash only) * '..' segments after split('/') One new Rust test covers all four cases. * fix(connection): isLan badge reflects active endpoint, not primary url useConnectionStatus.isLan was reading isLanUrl(server.url) — the *primary* address — so a dual-address profile that had fallen over to its public alternate kept advertising 'LAN' in the badge until the user looked at the server URL itself. Spec call-site-checklist line 25: 'active endpoint kind for badge (LAN vs extern)'. Now: ensureConnectUrlResolved returns probe.endpoint.kind on success; the hook tracks the latest kind in local state and surfaces that. Pre-first-probe fall-through keeps the old primary-URL classification so the badge has something to render at mount time. Three tests pin the three states (LAN-active after probe, public- active after fallback, primary-fallback before first probe completes); plus one for the online-event handler that invalidates the cache and re-probes. * fix(server): dedupe concurrent pickReachableBaseUrl calls for same profile Multiple call sites probe on roughly the same beat — useConnectionStatus 120-s tick + online handler + initial mount, switchActiveServer, bindIndexedServer, and ServersTab.testConnection. Two near-simultaneous probes for the same profile both observed an empty cache, both pinged every endpoint, and raced to write the sticky URL with last-write-wins. On a dual-address profile the slower probe could stomp the correct LAN sticky a millisecond after it was set. Now: an in-flight Map<profileId, Promise<PickReachableResult>>; a second call for the same id during an active probe returns the same promise instead of starting a fresh one. The finally-clear keeps the dedup window narrow (one settled probe → next call probes fresh). invalidateReachableEndpointCache deliberately doesn't touch the in-flight map — the racing probe's own finally will clean up. Three tests pin it: two concurrent calls share one ping; a fresh call after the previous settled does ping again; plus the existing shareBaseUrl two-LAN-with-flag-on test + the two-public-default test for completeness. * refactor(magic): extract magicPayloadAddressFields to single shared helper The lookup that turns a serverUrl into the v2-encode-ready { url, alternateUrl?, shareUsesLocalUrl? } shape was duplicated byte-identically between MagicStringModal.tsx and UserForm.tsx — both Navidrome admin user-mgmt encode sites. Workdocs §03 / §1a 'one source of truth for behavior'. Now lives in src/utils/server/serverMagicString.ts as a named export. Both call sites import + pass the current servers list (via useAuthStore.getState().servers) — keeps the helper pure so it's straight to unit-test if a third encoder ever appears. * fix(cover): wire cover:bucket-renamed listener for URL-change remigration cover_cache_rename_server_bucket emits cover:bucket-renamed on successful rename / merge, but no frontend listener was wiring it in. After a URL-change remigration the in-memory disk-src cache still held entries pointing at `{root}/{oldKey}/…/.webp` paths the disk no longer carries — the next read would serve a stale URL until the entry naturally aged out. New: forgetDiskSrcForServer(serverIndexKey) in diskSrcCache drops every cover entry under one server key in one pass (the existing forgetDiskSrcPrefix needs a non-empty coverArtId and can't blanket- clear a server). useCoverArtBridge subscribes to cover:bucket- renamed and calls it with oldKey. Tests: forgetDiskSrcForServer happy path, empty-key defensive no-op, no-match no-op; plus a regression-pin on the existing forgetDiskSrcPrefix so the two helpers don't drift in semantics. * test(dual-server): fill the high-impact coverage gaps from the branch review Adds the tests the review identified as missing on the hot-path UI flows + the partial-fail / alt-only edges: * AddServerForm.test.tsx (new) — five component tests: single-address save / dual-address save / two-LAN block-with- toast / v2 magic-string paste forwarding alt + share flag / edit-flow stripping alt+flag when the field is emptied. * Login.test.tsx (new) — v2 invite paste persists alternateUrl + shareUsesLocalUrl onto the saved profile; v1 invite leaves those fields undefined. * shareLink.test.ts — alternateUrl-only match for findServerIdForShareUrl (the dual-address paste case where the host shared the LAN URL via shareUsesLocalUrl=true); 'first hit wins' across two profiles where both match. * serverFingerprint.test.ts — partial-fail mix (folders+user ok, license+indexes rejected) so a Promise.allSettled regression wouldn't go silent. * cover_cache/mod.rs — rename_bucket_inner extracted as a testable FS-only helper (the Tauri command wrapper now just locks state + calls it + emits the event), plus six tests covering empty/unsafe keys, no-op-when-missing, no-op-when- equal, simple-rename, merge-with-prefer-existing. Also: every test fixture that I authored on this branch using 'frank' / 'frank@example.com' as a stand-in username/email swapped to 'tester' / 'tester@example.com' — keeping personal names out of test data is the codebase convention (see factories.ts) and is now a memory rule. * fix(test): typed mock access for pingWithCredentials in useConnectionStatus vi.mocked(...) returns the mock typed properly — bare .mock fails tsc because the imported function signature isn't a vi.Mock at import time. * docs(changelog): dual server address (PR #880) * fix(test): align diskSrcCache tests with main cover storage key API After rebase onto main, forgetDiskSrcPrefix takes a CoverArtRef-shaped argument and storage keys include cacheKind; merge coverDiskUrl tests from main with dual-address forgetDiskSrcForServer coverage.	2026-05-28 14:36:25 +03:00
cucadmuh	df3533bb5a	fix(cover): Windows thumbnails, tier fallback, PNG decode, coverArt id (#878) ... * fix(cover): tier fallback for sparse surfaces and Windows asset URLs Sparse UI (player bar, queue) now reads disk covers via the same tier ladder as dense grids, so a warm 800.webp satisfies a 128px request. Reject non-asset convertFileSrc results on Windows, widen Tauri asset scope, and seed ladder keys on cover:tier-ready. applyDiskPath uses seedGridDiskSrcCache only to avoid notify/subscriber infinite loops. * fix(artist): top-track thumb uses album coverArt already warm in grid Song coverArt ids often differ from album cover ids (e.g. Octastorium in the grid vs empty track thumb). Prefer the album row's coverArt on artist pages and ensure high priority for 32px dense cells. * fix(cover): albumId for playback/queue; no broken img until disk URL ready Prefer albumId over track-id coverArt (Navidrome). Wire queue to CoverArtImage with playback scope. CoverArtImage renders a placeholder div until asset src exists to avoid the browser broken-image icon. * fix(test): add song id to resolveArtistPageSongCoverArtId fixture Pick<SubsonicSong, …> requires id; fixes tsc in CI/build. * fix(cover): resolve albumId for Now Playing and artist top tracks Prefer albumId when album.coverArt echoes track id; use sparse surface on artist suggestion thumbs; apply resolveSubsonicSongCoverArtId across playback surfaces (Now Playing, fullscreen, mobile, mini). * fix(cover): decode PNG from Subsonic before WebP tier encode Enable `png` in the image crate — some servers return PNG cover art; failed decode left `.fetch-failed` and empty thumbs for those albums. * refactor(cover): consolidate cover id resolution and align tests Move resolveSubsonicSongCoverArtId helpers to src/cover/resolveCoverArtId.ts with resolvePlaybackTrackCoverArtId for player surfaces; co-locate tests; fix FullscreenPlayer expectations for albumId-first resolution. * docs: CHANGELOG and credits for PR #878 * fix(cover): keep per-track coverArt when distinct from song id Address PR #878 review (b): albumId only when coverArt is missing or echoes track id; pin case with unit test; comment isRawFsPath symmetry. * chore(cover): address PR #878 review nits (scope, tests, rename) Narrow asset scope to cover-cache dirs only; add diskSrcCache Windows-path tests; rename ArtistTopTrackCover; CHANGELOG symptom-first wording. * fix(cover): restore asset scope to app data dirs (Windows regression) $APPDATA/cover-cache/** did not match Tauri scope resolution — covers were blocked after load. Use $APPDATA/** and $APPLOCALDATA/** (no $DATA). * fix(cover): Windows asset URLs — restore DATA scope, path normalize Regression after review nits: dropped $DATA/** and strict isAssetProtocolUrl blocked valid http://asset.localhost URLs on Windows. Normalize C:/ paths before convertFileSrc; CoverArtImage/Hero hide broken img on load error. * fix(cover): disk peek fallbacks when cache folder id differs Small surfaces resolve albumId while cover-cache often stores WebP under track id or album.coverArt from the grid. Peek batch now tries legacy ids; playback scope resolves server index key by URL key, not UUID-only lookup. * fix(cover): Navidrome al-* vs mf-* disk id mismatch UI used mf-* coverArtId while library backfill only cached al-* folders. Prefer album id for display/peek when coverArt is mf-*; backfill now queues both distinct album_id and cover_art_id values. * fix(cover): mf→al disk peek when mf folder missing in cache Navidrome Subsonic often returns mf-* coverArtId while backfill only creates al-* folders. Peek mf first, then al-* from hints; load albumId from library when Subsonic omits it; ensure fallback uses al-* id. * feat(cover): CoverArtRef, segment disk layout, library-index backfill Normalize cover caching around stable entity ids from the local library and Navidrome fetch ids. Disk paths live in psysonic_core::cover_cache_layout (album/<entityId>/); UI uses CoverArtRef with cacheEntityId + fetchCoverArtId. - Remove SQLite/mf peek helpers (diskPeekIds, peekCoverOnDisk, mergeDiskIdHints) - Backfill reads album/artist rows from library SQLite (bare Navidrome ids ok) - Use stored cover_art_id for HTTP; per-disc dirs only when discs differ - Migrate call sites to albumCoverRef / albumCoverRefForPlayback * feat(cover): central CoverEntry resolver (artist, album, track) Add resolveEntry.ts and Rust CoverEntry helpers as the single source of truth for cache_entity_id vs fetch_cover_art_id. ref.ts delegates to them; resolveCoverArtId becomes a thin compatibility shim. * feat(cover): resolve cover entries from local library index Add library_resolve_cover_entry IPC and cover_resolve.rs so album, artist, and track covers use SQLite cover_art_id + disc detection. TypeScript helpers in resolveEntryLibrary.ts prefer the index over live API fields when rows exist. * feat(cover): library-first hooks for grids and playback UI Add useAlbumCoverRef, useArtistCoverRef, useTrackCoverRef, and usePlaybackTrackCoverRef — sync fallback then SQLite index upgrade. Wire album/artist cards, album header, song card, and all player surfaces to resolve covers from the local library when indexed. * feat(cover): complete library-first migration across all UI surfaces Add Album/Artist/TrackCoverArtImage, useLibraryCoverPrefetch, and batch resolve helpers. Migrate grids, search, home, playback sidecars, warm peek, playlists, and share flows to hooks that upgrade from SQLite. Backfill normalizes album rows through cover_resolve; document paths in COVER_PATHS.md. Radio remains a deliberate non-library exception. * fix(cover): stop render loop from unstable serverScope in library hooks Default param `{ kind: 'active' }` created a new object every render, so every grid cell re-ran library_resolve IPC and setState in a loop. Use COVER_SCOPE_ACTIVE singleton, coverScopeKey deps, and guarded sync updates. * chore(cover): remove COVER_PATHS.md from app tree (lives in workdocs) Audit doc is team spec — see workdocs 2026-05-cover-art-pipeline/cover-paths-audit.md. * fix(cover): unstick library backfill after route changes (PR #870 regression) useCoverNavigationPriority cleanup called beginNavigation instead of end, leaking navigationHoldDepth so ui_priority_hold never released and backfill never downloaded. Also skip disk check after cover_resolve normalization. * fix(cover): segment progress, cap backfill CPU, include artists in catalog Progress and disk size now scan album/ and artist/ segments (canonical 800.webp). Prune legacy flat server/al-* dirs on startup and backfill pass. Backfill: max 2 concurrent ensures; JPEG decode and WebP encode run on the blocking pool behind a shared 2-permit semaphore so Tokio workers stay cool. Artists were missing because the catalog only read the empty artist table; add distinct artist_id from track and album rows. Paginate with a composite (kind, id) cursor so album and artist rows are not skipped. * fix(cover): drop legacy prune; backfill per-disc and artist catalog Remove prune_legacy_* and cover_cache_catalog_entry — layout is only cover_dir (album|artist segments); stale flat dirs clear on LAYOUT_STAMP change. Backfill: artists from track/album artist_id; expand albums to per-CD mf-* slots when discs differ; fix resolve_album_cover_entry when album row is missing. * fix(cover): reduce library IPC storms and fix multi-disc player art Skip per-row library_resolve on live search and artist album grids; warm grids from API coverArt after mount instead of blocking layout. Dedupe and cap concurrent library_resolve calls. Restore per-disc cache keys in the player and queue when track mf-* art differs from the album bucket. * fix(cover): skip library resolve on advanced and full search rows Use API coverArt for album/artist rails and lazy viewport artwork so result pages do not fire hundreds of library_resolve IPC calls at once. * fix(cover): default libraryResolve off for browse grids and rails Skip per-card library_resolve on album/artist/song browse UI by default; keep it on album/artist headers, playback queue rows, and orbit approval. * fix(cover): split UI/backfill CPU pools and restore mainstage hero carousel Library backfill no longer shares the 2-permit JPEG/WebP semaphore with visible cover ensures. Hero initializes albums from props, re-binds scroll visibility after mount, updates backdrop on slide change, and uses library resolve for correct cover art on the banner. * fix(analysis): resume full-library scan after candidates phase Reset the SQL cursor when entering full-library mode so tracks with partial analysis are not skipped. Tighten TS backfill completion and CPU queue watermarking; align cover-cache key tests with album-scoped storage keys. * fix(library): remove useless map_err in cover_resolve (clippy) CI treats clippy::useless-conversion as error on rusqlite optional() chains. * fix(cover): satisfy clippy on cover_cache_ensure IPC args Pass CoverCacheEnsureArgs as a single Tauri parameter instead of nine positional fields; align frontend invoke payload with { args }.	2026-05-28 03:15:08 +03:00
cucadmuh	418b25914a	feat(cover): unify cover pipeline and stabilize mainstage/now-playing (#870) ... * chore(cover): scaffold cover module and rust cover_cache stub Wave 0: src/cover/ skeleton per contracts.md §12, stub IPC commands in cover_cache/mod.rs (no-op returns until phase B). * feat(cover): add unified cover module and tier resolver (phase A) Wave 1A: tiers, storage keys, resolveJs with cold/sibling races, useCoverArt, CoverArtImage, layoutSizes, playback scope helpers, coverSiblings tier ladder, deprecated shims on subsonicStreamUrl. * feat(cover): rust disk cache and tier-ready events (phase B) Wave 1B: cover_cache module with WebP tier encode, HTTP canonical 800 fetch, cover_cache_* commands, cover:tier-ready / cover:evicted events, disk layout tests. * feat(cover): prefetch hook, tier-ready handoff, library backfill IPC (phase B/C) Wave 2: useCoverArtPrefetch, cover:tier-ready/evicted bridge, one-time IDB cover key clear, prefetch registry drain, MainApp wiring. * feat(cover): migrate dense grids to CoverArtImage and prefetch (phase D) Wave 3A: dense surfaces use layout-native displayCssPx, surface=dense, coverPrefetchRegister on Home/Albums/search; AlbumCard cell width from grid. * feat(cover): migrate sparse surfaces and integrations (phase E sparse) Wave 3B: sparse CoverArtImage/useCoverArt, lightbox tier 2000, ArtistHeroCover, MPRIS/Discord/export integrations, playback chrome and detail heroes. * feat(cover): revalidation scheduler and disk pressure gate (phase E+) Wave 4: coverCacheMaxMb settings (en/ru), StorageTab disk usage, cover_cache_configure, useCoverRevalidateScheduler, playbackServer uses cover fetchUrl; pressure watermarks. * docs: CHANGELOG and credits for cover art pipeline PR #869 * fix(cover): stop webview getCoverArt storm on dense grids (429) Dense surfaces no longer put rotating getCoverArt URLs in img src; load disk via Rust ensure + convertFileSrc. Tier-ready notifies listeners instead of invalidating IDB. Throttle background prefetch and cap Home registry. * fix(cover): omit empty img src until cover URL is ready React 19 warns on src=""; CoverArtImage uses undefined until disk/IDB resolves; queue current track shows placeholder when src is still empty. * fix(cover): disk cache by host index key, parallel ensure, asset protocol Bind cover storage to serverIndexKey (library host), rename cover IPC/events, fix REST base URL and Tauri flat args, enable protocol-asset for disk paths, add prioritized ensure queue, and wipe legacy profile-UUID cache once. Limit Vite dep scan to index.html so research/target HTML is ignored. * fix(cover): WebP tiers, disk peek, home cache, asset URLs for mainstage Encode lossy WebP (~82), write only missing tiers, library cover backfill, and cover_cache_peek_batch for fast paint from disk. diskSrcCache + CSP asset protocol; no IDB fallback when server is up. Session Home feed cache with warm peek on return; BecauseYouLike deduped cover hook and high prefetch. * feat(cover): per-server cache strategy and native library backfill Move cover disk cache settings to Offline & cache with Lazy/Aggressive per server, per-server clear, and no size cap. Run full-catalog backfill on the Rust runtime (sync-idle wake, bounded HTTP, bulk 800px writes without flooding the webview). Drop global prefetch limits from auth store and waveform clear from the offline storage block. * fix(build): CSP connect-src for Subsonic API; quieter prod nix build Prod webview blocked axios ping after cover CSP (missing connect-src). Drop cargo tauri -v in flake build, raise Vite chunk limit, ignore tsbuildinfo. * fix(cover): complete WebP ladder in library bulk backfill Aggressive backfill now writes all derived tiers (128–800), skips IDs only when the full ladder exists (not 800 alone), avoids fetch-failed markers on bulk HTTP errors, and stops the pass when the active server changes. * fix(cover,home): navigation-priority backfill and Because You Like UX Pause library cover backfill while navigating; split peek/ensure traffic so grids and rails win over bulk work. Disk src lookup, grid warm hooks, and non-blocking mainstage prime for faster visible covers. Because You Like: session snapshot, staggered horizontal skeleton row, text hidden until cover is ready, and layout aligned with loaded cards. * feat(random-albums,library): local-first album fetch + cover art pipeline Random Albums теперь запрашивает локальный SQLite-индекс (ORDER BY RANDOM() LIMIT N) вместо сетевого запроса к серверу. При готовом индексе спиннер исчезает практически мгновенно; сеть используется только как фолбэк. - advanced_search.rs: добавляет `("random", _) => RANDOM()` в allowlist сортировок - browseTextSearch.ts: runLocalRandomAlbums — SQLite-рандом для Albums - RandomAlbums.tsx: doFetchRandomAlbums local-first для обоих путей (без жанра и с жанром через runLocalAlbumsByGenres + JS-shuffle); speculative reserve прогревает следующий батч в фоне после каждого Refresh Также: обновление пайплайна обложек (coverTraffic, peekQueue, ensureQueue, diskSrcLookup, warmDiskPeek, prefetchRegistry, useCoverArt, useWarmGridCovers, useCoverNavigationPriority, resolveIntersectionScrollRoot и сопутствующие компоненты/хуки). * fix(random-albums): prevent double-load on Zustand rehydration useEffect([selectedGenres, load]) fired twice on every visit: first with default store values, then again ~50 ms later when Zustand rehydrated mixMinRatingFilterEnabled/minAlbum/minArtist from localStorage. Previously this was invisible because the first network fetch took ~1.5 s, so loadingRef.current was still true on the second fire. With the new local-first SQLite path the first load completes in ~50 ms, leaving the guard cleared before rehydration triggers a second random batch. Fix: ref-pattern — keep loadRef.current fresh on every render, effect depends only on selectedGenres. Manual Refresh and genre-filter changes still call the latest closure correctly. * fix(random-albums): stop warmCoverDiskSrcBatch in fillReserve from causing visual flash fillReserve вызывал warmCoverDiskSrcBatch для обложек резервного батча, что вызывало bumpDiskSrcCache() для каждой новой обложки (~30+ вызовов). Это будило всех подписчиков useCoverArt на текущей странице, провоцируя видимую перерисовку примерно через ~1.5 с после загрузки (когда filterAlbumsByMixRatings делает сетевые запросы к рейтингам артистов). - fillReserve: убран warmCoverDiskSrcBatch — обложки прогреваются лениво при consume резерва через primeAlbumCoversForDisplay - reserve-путь в load(): добавлен primeAlbumCoversForDisplay перед setAlbums (аналогично non-reserve пути; при уже прогретом кэше — мгновенно) * feat(because-you-like): reserve-first pattern — instant display on return visits Каждый визит на Mainstage после первого теперь отдаёт готовую заготовку мгновенно, вместо spinner → сетевые запросы → контент. Архитектура: - resolvePicks / fetchBecauseYouLike вынесены на уровень модуля (выход из замыкания useEffect); читают текущий localStorage, возвращают { anchor, recs, nextAnchorHistory, nextPicksHistory } - fillBecauseReserve — fire-and-forget фоновая функция: запускается сразу после отображения результата, кладёт следующий батч в _becauseReserve. Covers намеренно не прогреваются (bumpDiskSrcCache на текущей странице не нужен); они прогреваются через primeAlbumCoversForDisplay при consume. - useLayoutEffect: если reserve готов — не сбрасывает стейт в skeleton (контент появляется без мигания) - useEffect: reserve-first path — consume → primeCovers → setState → fill; full-fetch path сохранён как fallback при первом визите или промахе Поведение: - Визит 1: full fetch (как раньше) → показ → fillReserve R1 - Визит 2+: consume R1 → мгновенный показ → fillReserve R2 - При сетевом сбое: restore из session cache (как раньше) * fix(because-you-like): initialise state from reserve — no skeleton flash on remount При ремаунте компонент стартовал с refreshing=true/anchor=null/recs=[] и показывал skeleton на один тик до того как useEffect отработает. Теперь useState() использует lazy initializers, которые читают _becauseReserve прямо в первом рендере: если reserve валиден — state сразу refreshing=false, anchor=X, recs=[...] и skeleton не показывается вообще. Covers уже в diskSrcCache (из предыдущего показа) и появляются без дополнительных запросов. useLayoutEffect упрощён: вызывает hasValidReserve() и сбрасывает в skeleton только если reserve отсутствует (для случая navigation без ремаунта). * fix(because-you-like): apply reserve in useLayoutEffect to handle async pool arrival Lazy initializers не могли применить reserve при первом рендере, потому что mostPlayed/recentlyPlayed/starred приходят из Home.tsx асинхронно — pool=[] на первом рендере, poolKey не совпадает с reserve. useLayoutEffect теперь активно ставит стейт из reserve (а не просто не сбрасывает): когда pool обновляется до реальных данных, useLayoutEffect срабатывает синхронно до paint, проверяет reserve и сразу применяет anchor/recs/refreshing=false. При отсутствии reserve — сбрасывает в skeleton как прежде. * fix(because-you-like): reserve > cache > skeleton — eliminate skeleton flash on mount Корневая причина: Home.tsx загружает mostPlayed асинхронно через useEffect, поэтому на первом рендере pool=[], poolKey=''. Reserve хранится с реальным poolKey → mismatch → lazy initializers запускали skeleton. Теперь двухуровневый fallback без зависимости от poolKey: 1. reserve (serverId + poolKey совпадают) → мгновенный новый батч 2. becauseYouLikeCache (только serverId) → stale-while-revalidate, контент доступен сразу с mount, обновляется тихо в фоне 3. skeleton → только при полном отсутствии данных (первый визит) Применяется одинаково в lazy useState initializers, useLayoutEffect и full-fetch path useEffect (не сбрасывать в skeleton пока есть cached контент). * fix(because-you-like): key reserve by serverId only; guard useEffect on empty pool Проблема: reserve хранился с poolKey, но на первом рендере pool=[] → poolKey='' → mismatch → показывался кэш (предыдущий набор) ~500ms пока Home.tsx не загружал mostPlayed. Исправления: - BecauseReserve: убран poolKey — reserve валиден для любого pool-состояния на том же сервере. Pool (топ-артисты) меняется медленно; один раз показать reserve с чуть устаревшим anchor лучше чем показывать предыдущий набор 500ms - hasValidReserve: проверяет только serverId - fillBecauseReserve: убран poolKey из сигнатуры и хранилища - useEffect: guard pool.length === 0 → возврат без fetch/consume; effect перезапустится когда pool заполнится (реальные deps изменятся) → reserve применяется из useLayoutEffect ещё до pool, без стале-флэша Итоговый порядок: reserve (instant, serverId) > cache (stale-while-revalidate) > skeleton (только первый визит) * fix(home): remove mix-rating deps from feed useEffect — prevent Zustand rehydration double-fetch Корень: useAuthStore(mixMinRatingFilterEnabled/Album/Artist) были в deps useEffect. Zustand persist реhydrates асинхронно — сначала activeServerId, потом mix-rating значения. Это вызывало двойной запуск эффекта: - Первый запуск: homeFeedCache hit → показывает набор предыдущего просмотра - Второй запуск (после rehydration): cache miss или повторный fetch с реальными mix-настройками → ~500ms → новый набор Итог: Hero, AlbumRow, BecauseYouLikeRail показывали предыдущий набор первые ~500ms при каждом возврате на Mainstage. Fix: убраны mixMinRatingFilterEnabled/Album/Artist из deps. getMixMinRatingsConfigFromAuth() читается внутри эффекта через getState() — всегда актуальные значения без пересоздания замыкания. Mix-настройки по-прежнему применяются при fetch, но не вызывают двойной запуск при rehydration. * feat(home): local-first discover songs via SQLite ORDER BY RANDOM() Добавлена runLocalRandomSongs (аналог runLocalRandomAlbums для треков) в browseTextSearch.ts — использует libraryAdvancedSearch с sort random, field уже поддерживается Rust-кодом через wildcarded ("random", _) ветку. В Home.tsx: discoverSongs теперь сначала пробует локальный индекс, и только при недоступности (индекс не готов, ошибка) падает обратно на getRandomSongs.view. Ускоряет первую загрузку Mainstage — треки берутся из SSD вместо сети. * fix(home): pre-populate state from cache at mount — eliminate empty-state flash on return visits Причина: Home.tsx размонтируется при навигации. При возврате первый рендер всегда с пустыми массивами (heroAlbums=[], mostPlayed=[] и т.д.), потом useEffect читает homeFeedCache и заполняет state. Даже один кадр с пустым состоянием вызывает перерисовку Hero и BecauseYouLikeRail (pool=[]). Решение: getInitialHomeFeed() читает homeFeedCache синхронно через useAuthStore.getState() (не hook) в lazy useState initializers. К моменту повторного визита store уже rehydrated — все state получают кэшированные данные до первого рендера. Дополнительно: wasPrePopulated предотвращает повторный applyFeedSnapshot в useEffect когда state уже заполнен — иначе новые ссылки на массивы вызывали бы ненужные ре-рендеры дочерних компонентов с теми же данными. * fix(mainstage): keep refresh without return flicker Keep Home and Because You Like visually stable during a single visit while still refreshing data for the next re-enter. Improve mainstage cover warmup by ensuring and pre-decoding above-the-fold artwork so hero and top rails appear instantly after navigation. * fix(mainstage): stabilize because rail and hero background framing Measure Because You Like layout before first paint to avoid width snap flicker, and render hero background as centered cover-fit images so the frame no longer jumps from top to middle on mount. * fix(now-playing): prewarm track data and prevent stale carry-over Warm Now Playing fetch caches and playback cover art on track change so entering the page no longer waits on first-load requests. Gate key-based sections (top songs, tour, Last.fm) by the active track/artist keys to avoid briefly rendering values from the previous track. * fix(cover,test): refresh playback scope and default tauri cover mocks Recompute playback cover scope when queue/server context changes so now-playing art resolves against the correct server after handoffs. Add default cover-cache invoke handlers to the shared Tauri test harness to prevent unhandled rejections in suites that mount cover-aware UI. * fix(cover,now-playing,test): align prewarm scopes and tighten tauri mocks Make cover-cache invoke defaults opt-in for tests, align radio prewarm scope with active rendering scope, and add targeted hook tests for prewarm + playback-scope reactivity. Also harden Rust cover URL building to avoid panic on malformed base URLs. * test(cover): hoist mocked useCoverArt and clean EOF whitespace Fix the new playback-scope hook test to use a hoisted vi.mock-safe stub and keep branch-wide diff checks clean by removing an accidental trailing blank line. * fix(cover): align playback ensure auth and harden backfill retry flow Use playback-server credentials for playback-scoped cover ensures, persist fetch-failed markers for bulk library backfill failures, and avoid advancing backfill cursor when UI-priority hold interrupts a batch. * fix(ci): resolve clippy lint and update frontend node runtime Move fetch helper before the test module to satisfy clippy's items-after-test-module rule, and modernize frontend CI to setup-node v6 with lts/* instead of pinned Node 20. * chore(settings): simplify cover and analytics strategy copy Move strategy summaries below tables, simplify Lazy/Aggressive wording, keep analytics warning always visible, and localize Russian texts to plain language without technical jargon.	2026-05-26 19:35:08 +03:00
cucadmuh	11974e1438	feat(analysis): ship index-key rebuild, strategy controls, and playback/queue pipeline updates (#864) ... * feat(analysis): align index settings and per-server strategies Rebuild the local index UX to live under Servers with per-server analytics strategies, and scope analysis queue hints/pruning by playback server so priorities stay isolated across profiles. * feat(analysis): add progress tracking and server analysis deletion functionality Introduce new interfaces for tracking library analysis progress and reporting on server analysis deletions. Implement functions to retrieve analysis progress for a server and to delete all analysis data for a specified server, enhancing the analytics strategy section with real-time progress updates and management capabilities. Update relevant components and localization files to support these features. * feat(server): implement server index key migration and enhance server ID resolution Add functionality to migrate server index keys from legacy IDs to new URL-based keys, improving server ID resolution across the application. Introduce new types and commands for handling server key migrations in both analysis and library contexts. Update relevant functions to utilize the new server ID resolution logic, ensuring consistency and accuracy in server-related operations. * refactor(library): simplify server ID handling in sync progress and idle subscriptions Refactor the library sync progress and idle subscription functions to directly use the payload's server ID without additional mapping. Update related components to resolve server IDs using a new utility function, ensuring consistent server ID resolution across the application. This change enhances code clarity and maintains functionality. * refactor(analytics): rename advanced strategy to aggressive and update descriptions Refactor the AnalyticsStrategySection component to rename the 'advanced' strategy to 'aggressive' for clarity. Update related localization strings to reflect this change, enhancing the user experience by providing clearer descriptions of the analytics strategies. Additionally, remove unused strategy description functions to streamline the code. * fix(audio): update server ID handling in audio progress functions Refactor the audio progress handling to utilize the new `getPlaybackIndexKey` function for server ID resolution. This change ensures that the correct analysis server ID is used when processing audio progress, enhancing the accuracy of playback operations. Additionally, a minor update was made to the analysis cache to include a checkpoint after seeding from bytes. Update the library path in live search to reflect the new database structure. * refactor(analysis): update server ID handling and drop legacy keys Refactor server ID handling across analysis components to utilize scheme-less keys (host + optional path) instead of legacy scheme-based keys. Introduce SQL migrations to drop legacy analysis rows and library entries keyed by scheme URLs. Update relevant functions and tests to ensure consistent server ID resolution and remove references to the legacy '' scope, enhancing clarity and maintainability. * refactor(migration): switch to strategy C dual-db flow Replace destructive server-key migration paths with a blocking inspect/run pipeline that imports into v2 sqlite files, verifies data, then switches active databases with backup safety. Add frontend migration orchestration and post-switch key rewrites while preserving existing user settings behavior. * fix(migration): harden runtime db switch and startup gate Switch database promotion through live runtime store/cache connection swaps so migration cannot leave writers on old sqlite inodes, and tighten startup gating to block initialization until migration completes. Also fix empty-bucket warning detection and set the done flag only after a post-run inspect confirms no pending legacy rows. * feat(migration): enhance migration reporting with skipped server rows tracking Add new fields to migration interfaces and reports to track skipped rows for removed servers. Update relevant components to display warnings and log messages when such rows are encountered during migration processes, improving visibility and user awareness of migration status. * fix(migration): avoid startup blocking modal on no-op runs Keep migration gate completed by default after successful runs and perform done-flag inspections without forcing a blocking phase, so normal app startup no longer flashes migration preparation when no migration is needed. * fix(migration): enforce startup precheck and purge unknown rows Prevent stale done-flag bypass by starting migration state in idle and gating completion on orchestrator precheck, and delete unknown removed-server rows from v2 databases before switch so skipped rows are not carried into the new active DB. * fix(migration): block UI during done-flag precheck Set inspecting phase before the first migration inspection and treat idle as blocking in the migration gate, so startup precheck cannot render the app before migration status is confirmed. * fix(migration): hide precheck modal when no migration is needed Keep startup precheck in a non-blocking idle phase and show the migration modal only after inspect confirms real migration work, removing the recurring half-second migration flash for already-migrated users. * fix(migration): cleanup legacy db files after path migration Always remove legacy analysis and library sqlite files (including wal/shm sidecars) when the new database paths are active, so old-path artifacts from previous builds do not linger after migration. * docs(changelog): add PR #864 release notes and contributor credit Document the full index-key rebuild scope for 1.47.0 and add the corresponding settings credit entry for PR #864. * test(analysis): raise hot-path coverage for analysis cache Add focused unit tests for analysis cache compute/store hot paths and edge branches so coverage regressions are caught before CI. Make AppHandle entrypoints runtime-generic and enable tauri test utilities in dev dependencies to cover no-cache and registered-cache execute paths. * fix(migration): make rebind pass resilient to foreign key ordering Run library and analysis server_id rebind operations inside a foreign-key-disabled transaction and validate with PRAGMA foreign_key_check after commit, so migrations from older databases do not fail on transient FK ordering during bulk updates. * feat(backup): add dual-database backup flow and blocking UX Extend backup/export and restore flows to handle library databases with unified archive detection and asynchronous backend execution. Improve backup UI with a global blocking modal and clearer localized copy so long operations do not look like app hangs. * docs(changelog): add PR #864 backup notes and contributor credit Update 1.47.0 release notes with backup/restore UX and archive-flow entries for PR #864, and add the matching settings credits contribution line for cucadmuh. * docs(changelog): sort 1.47.0 entries from old to new Reorder Added, Changed, and Fixed subsections in the 1.47.0 changelog so entries follow chronological PR order inside each block. * fix(playback): align offline/hot cache lookup with indexKey scope Use a canonical playback cache key based on indexKey with legacy UUID fallback so migrated offline and hot-cache entries are still resolved on normal play, resume, queue-undo, and prefetch paths. Refresh PR #864 changelog/credits text to reflect the full migration and backup scope.	2026-05-24 21:11:04 +03:00
cucadmuh	45e0e1206f	fix(playback): pin queue playback to source server when browsing another library (#717) ... * fix(playback): pin queue streams, cover art, and library links to queue server When the active server changes while a queue from another server is playing, keep streams and UI on queueServerId; switch back for artist/album links and queue or player-bar context menus. * fix(playback): switch to queue server when opening Now Playing Ensure active server matches queueServerId before Subsonic fetches on the Now Playing page, mobile player route, and queue info panel; scope caches by server id. * docs(credits): mention Now Playing in PR #717 contribution line * fix(playback): route scrobble and queue sync to queue server Address PR review: apiForServer for scrobble/now-playing/savePlayQueue, clear queueServerId on server removal, mini-player queueServerId sync, block cross-server enqueue with toast, and regression tests.	2026-05-15 16:08:41 +03:00
Maxim Isaev	e7431b94b8	feat(search): queue pasted share links from Live Search and mobile search ... Implement share-link detection in search (track, queue, album, artist, composer): enqueue tracks/queues without interrupting playback; preview album/artist/composer without switching the active server; queue preview modal with scrollable track list. Based on community PR #551. Co-authored-by: Daniel Wagner <daniel.iuser@icloud.com>	2026-05-15 13:38:35 +03:00
Frank Stellmacher	9606a99efb	refactor(api): F.50 — extract 7 small domain modules (#615) ... Seven domain-eng splits peel ~200 LOC of read endpoints out of `api/subsonic.ts`: - `subsonicStreamUrl.ts` — `buildStreamUrl`, `coverArtCacheKey`, `buildCoverArtUrl`, `buildDownloadUrl` (token-signed URL builders for the four /rest endpoints we hand to the browser). - `subsonicStarRating.ts` — `getStarred`, `star`, `unstar`, `setRating`, `probeEntityRatingSupport`. `setRating` still triggers the lazy `navidromeBrowse` cache invalidation; the same-folder lazy import path is preserved. - `subsonicSearch.ts` — `search`, `searchSongsPaged`. - `subsonicScrobble.ts` — `scrobbleSong`, `reportNowPlaying`, `getNowPlaying`. - `subsonicAlbumInfo.ts` — `getAlbumInfo2`. - `subsonicLyrics.ts` — `getLyricsBySongId`. - `subsonicGenres.ts` — `getGenres`, `getAlbumsByGenre`. 63 external call sites migrated to direct imports. Four `vi.mock` targets in the store-level tests pointed at `../api/subsonic` and were updated to the new module paths. Pure code-move. subsonic.ts: 762 → 561 LOC (−201).	2026-05-13 00:46:13 +02:00