feat: add per-launch Emby endpoint override for LAN soak A/B - #55
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
HYPERWALL_SERVER_URLfor a per-launch Emby endpoint override without mutatingconfig.ini.Grounded investigation
PR #54's M5 soak fixed the UI stalls. Greg-side evidence shows Emby can transcode
demon_mika_compilation_1at ~9.8x, while the client usesmb.perseus.observerand reports TLS I/O, repeated range reconnects/client disconnects, and cache starvation. This PR enables a controlled LAN endpoint A/B againsthttp://10.168.168.29:8096without changing saved credentials or normal endpoint settings.Validation
python3 tests/run_all.py— PASSgit diff --check— PASSTest command on M5