Skip to content

Fix media wall reliability - #5

Merged
kevinplus66 merged 4 commits into
mainfrom
agent/media-wall-reliability
Jul 12, 2026
Merged

Fix media wall reliability#5
kevinplus66 merged 4 commits into
mainfrom
agent/media-wall-reliability

Conversation

@kevinplus66

Copy link
Copy Markdown
Owner

Summary

  • correct media-wall region, year, identity, poster, source-health, and refresh scheduling behavior
  • improve Home empty/error states, poster retry, detail freshness, diagnostics, and polling
  • harden poster proxying and cache delivery while keeping media-wall reads cache-only
  • expose runtime media-wall configuration and update deployment documentation

Root cause

Cached source health, metadata identity conflicts, and region/year heuristics were handled independently, allowing stale or conflicting data to survive into rails. The frontend then treated several incomplete/error states as ordinary empty content.

Validation

  • python -m pytest -q — 312 passed
  • npm run test --prefix frontend — 77 passed
  • npm run lint --prefix frontend
  • npm run build --prefix frontend
  • OpenAPI and generated TypeScript drift checks
  • live j1900 snapshot replay against the new sanitizer

@kevinplus66
kevinplus66 marked this pull request as ready for review July 12, 2026 21:19
@kevinplus66
kevinplus66 merged commit 91600e1 into main Jul 12, 2026
2 checks passed
@kevinplus66
kevinplus66 deleted the agent/media-wall-reliability branch August 22, 2026 08:11
kevinplus66 added a commit that referenced this pull request Aug 22, 2026
- Return 404 for missing /_next assets instead of serving index.html
  through the SPA fallback; the old path let an HTML response get cached
  at an asset URL with a one-year immutable header.
- Clear stale country filter values when country options are
  unavailable, so URL-derived filters cannot stay active while hidden.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant