Repository navigation
v0.6.33: Recover stable frontend after v0.6.32 white screen - #47
Merged
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
1 participant
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.
Recovery hotfix after v0.6.32 produced a clean-load white screen after Ctrl+F5. This does not attempt another runtime-sensitive Multi-Position frontend patch. Instead it restores the panel module entrypoint to the runtime-confirmed v0.6.31 frontend, removes the unstable kcc-soundlab-panel-0632.js wrapper, and bumps the integration to v0.6.33. The read-only multi_position_api.py backend introduced in v0.6.32 remains registered but unused by the frontend, so no measurement/tuning data is removed. Repeatability, Confidence, Guards, Prediction, Apply Preview, Apply/Restore, snapshots, channel EQ, Store version and Goldhorn isolation are unchanged.