fix: restore imported libraries and directory-user flows #2
Loading…
Reference in a new issue
No description provided.
Delete branch "fix/ldap-crypto-provider"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Imported libraries could not finish their native rebuild, directory login could panic before authentication, and the official Web stalled on catalog and name queries. This bundle repairs those observed failures while preserving imported identities, user state and the Jellyfin client contracts.
Validation: full
just gatepassed with 612 Rust and 192 Node tests, none failed or ignored; all 48 Python import tests passed. The native host release build passed with unchanged production defaults, Fat-LTO and CGU1 (12 min 11 s during concurrent verification; this is not an isolated compiler comparison or an AMD64-image proof).The full restored real PostgreSQL dataset preserves protected imported data and 90,204 assets/21,979,647,374 bytes by SHA. All 21,348 physical media DTOs pass actual HTTP GET validation in 743.215 s. The repeated API comparison preserves counts and observed result sets. Actual LLDAP plus unchanged deployed Web assets pass login, home, 100-film library, movie detail, real search, all 19 read-only native module pages, authenticated query-only WebSocket and logout. A separate fresh Web scenario covers v13 API-key creation/use/revocation and persistent module/SSE/OMDb/Webhook forms.
Observed search prerequisites now take 0.630/0.564 s for persons and 0.031/0.024 s for studios. An unfiltered 20-person page still spends approximately 27 s computing the complete 37,594-person scope; this remaining latency is documented. Evidence and exact scope:
docs/migration/jellyfin-import.md.The PR must complete AMD64 production build/runtime CI before merge. New-image cluster acceptance follows through GitOps: resume the real scan/keyframe rebuild, then verify API playback and Intel hardware on actual files. Existing v0.2.0 hardware probes do not substitute for that final new-image proof.