You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Upstream MUIO has moved past v5.5. Four "MUIO ver 5.6" commits landed in early April, and one more on May 5 reworked the new "indicators" feature. I'm treating that May 5 commit as part of the v5.6 set since it changes the same code.
I checked what it would take to bring this in by simulating the merge from where MUIOGO is today.
This issue is the tracker for that work.
The rule is the same as the v5.5 sync (#388, #393): follow upstream by default, and only deviate where MUIOGO has to keep something working that upstream doesn't care about — portability, security, our setup flow, that kind of thing.
A few things worth knowing up front:
MUIOGO is still labelled "MUIO 5.5" everywhere; this sync moves us to 5.6
upstream's current code reads two config files (Indicators.json and Duals.json) that they forgot to commit, so the app crashes on first run if you take it as-is — we'll add small safety checks until upstream ships the missing files
the new "Save" button on the Config page sends extra data that an existing MUIOGO callsite doesn't know to provide; easy to miss, easy to break
The work is split into five sub-issues, sub-PRs target a long-lived feature/v56-ui-sync branch (already pushed), and the final merge from feature/v56-ui-sync to main is the last step (mirrors #422).
Upstream MUIO has moved past v5.5. Four "MUIO ver 5.6" commits landed in early April, and one more on May 5 reworked the new "indicators" feature. I'm treating that May 5 commit as part of the v5.6 set since it changes the same code.
I checked what it would take to bring this in by simulating the merge from where MUIOGO is today.
This issue is the tracker for that work.
The rule is the same as the v5.5 sync (#388, #393): follow upstream by default, and only deviate where MUIOGO has to keep something working that upstream doesn't care about — portability, security, our setup flow, that kind of thing.
A few things worth knowing up front:
Indicators.jsonandDuals.json) that they forgot to commit, so the app crashes on first run if you take it as-is — we'll add small safety checks until upstream ships the missing filesThe work is split into five sub-issues, sub-PRs target a long-lived
feature/v56-ui-syncbranch (already pushed), and the final merge fromfeature/v56-ui-synctomainis the last step (mirrors #422).Sub-issues:
HelpersClass.py,Modals.html, and stubIndicators/DualsJSONs (no dependencies — start here)DataFileClassandOsemosysClass, keep MUIOGO solver code (depends on [Task] Port HelpersClass.py, Modals.html, and stub Indicators/Duals JSONs for v5.6 #458)Duals/Indicatorsdata (depends on [Task] Port HelpersClass.py, Modals.html, and stub Indicators/Duals JSONs for v5.6 #458)Order: #458 first; #459, #460, #461 can run in parallel after; #462 lands last.
Done when:
feature/v56-ui-sync→mainis merged./scripts/setup.sh --checkand./scripts/smoke.shpassVersions.htmlandWebAPP/index.htmlreflect "MUIO 5.6"Related:
docs/UPSTREAM_SYNC.md