| Name |
Last commit
|
Last update |
|---|---|---|
| .. | ||
| api | ||
| escales | ||
| manifeste | ||
| semaphore | ||
| tasks | ||
| tide-table | ||
| ui | ||
| .gitignore | ||
| DESIGN.md | ||
| PRODUCT.md | ||
| README.md | ||
| ardour_faders.json | ||
| serve.py | ||
| setlist_opal2026.txt |
catalog.generated.json was stale since 2026-06-23 (73 tracks / 23 gigs) and
missing opal-festival-2026 + cosmicfest-2026 entirely — it never got rebuilt
after catalog_view.json picked those gigs up on 2026-09-02. Re-ran the
pipeline (build_catalog_view.py then build_catalog.py):
catalog_view.json: 81 tracks / 25 gigs / 63 takes (unchanged — was
already current, only as_of + minor EDA-coverage
deltas moved)
catalog.generated.json: 73→81 tracks, 23→25 gigs, now carries both missing
2026 gigs, both validate clean against models.Catalog,
and track-id sets match view↔ generated exactly
(no silent drops either direction)
Root cause of the as_of staleness: build_catalog_view.py hardcoded
`AS_OF = "2026-06-06"` as a literal instead of stamping the actual build
date, so every regeneration since kept reporting the same frozen date no
matter when it ran. Now computed as `date.today().isoformat()`. Checked the
other suspected bug (a next/content/lives hardcoded path) — not present;
LIVES already points at .../www/content/lives without next/ since 6e51fff.
| Name |
Last commit
|
Last update |
|---|---|---|
| .. | ||
| api | Loading commit data... | |
| escales | Loading commit data... | |
| manifeste | Loading commit data... | |
| semaphore | Loading commit data... | |
| tasks | Loading commit data... | |
| tide-table | Loading commit data... | |
| ui | Loading commit data... | |
| .gitignore | Loading commit data... | |
| DESIGN.md | Loading commit data... | |
| PRODUCT.md | Loading commit data... | |
| README.md | Loading commit data... | |
| ardour_faders.json | Loading commit data... | |
| serve.py | Loading commit data... | |
| setlist_opal2026.txt | Loading commit data... |