Repository navigation
v0.6.31: Recover Repeatability frontend and harden JS validation - #45
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 for the v0.6.30 clean-load white screen. The v0.6.30 Repeatability frontend contained a JavaScript template/ternary syntax error in the Measurement Repeatability heading. Existing CI stayed green because it only ran
node --checkon six legacy frontend files and never parsed versioned entrypoints. v0.6.31 replaces the active v0.6.30 frontend chain with a clean recovery module built directly on the runtime-confirmed v0.6.29 chain, preserves persistent repeat-response API/storage and repeatability analysis, removes the broken v0.6.30 entrypoints, bumps integration version, and changes CI to syntax-check every frontend.jsfile. No changes to primary REW storage, EQ Assistant Apply/Restore, snapshots, crossover/null guards, channel EQ, Store version, model.py, or Goldhorn control.