Skip to content

Missing VideoEnhanced.hyp in hyp-files and pipeline gap detection #2

@madjin

Description

@madjin

Summary

videoenhanced is present in manifests/catalog metadata, but its source .hyp file is missing from hyp-files/, resulting in a non-downloadable entry.

Current Evidence

  • context/hyp_index.raw.json has an entry for VideoEnhanced.hyp with:
    • status: "pending"
    • local_path: null
  • context/apps/videoenhanced/manifest.json points to source.hyp_filename: "VideoEnhanced.hyp"
  • hyp-files/VideoEnhanced.hyp does not exist
  • catalog/catalog.json currently shows for videoenhanced:
    • hyp_filename: "VideoEnhanced.hyp"
    • download_path: null
    • has_download: false

Why This Matters

  • Catalog can include entries that appear complete but have no downloadable .hyp artifact.
  • This should be detected and surfaced earlier in ingestion/build pipeline.

Repro

  1. Run:
    • python3 scripts/catalog/build_explorer_data.py
  2. Observe failure:
    • Missing .hyp reported for videoenhanced
    • Non-zero exit code in strict mode

Desired Behavior

  • Pipeline should fail as soon as a manifest references a missing hyp-files/*.hyp (default strict mode).
  • Build output should include a machine-readable report of missing files.
  • CI should block merges/releases when missing .hyp artifacts exist.

Suggested Follow-ups

  1. Fix ingestion/download stage so VideoEnhanced.hyp is retrieved (or remove the app entry intentionally).
  2. Add CI gate to run strict build and fail on missing .hyp.
  3. Keep/report missing artifacts in a stable location (tmp/manifests/missing-hyp-files.json) for debugging.

Acceptance Criteria

  • hyp-files/VideoEnhanced.hyp exists OR videoenhanced is intentionally removed from published catalog.
  • Strict build passes without missing .hyp errors.
  • CI fails if future missing .hyp regressions occur.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions