Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

[PROPOSAL] The C-vs-Rust dual-build comparison from #2207 never runs; the C-only build drops 708 and HEVC captions

Aperta
  • Qualcosa non va?
#2,398 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
35/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
c, github-actions, rust
Ambito
ci-cd, testing-qa

Direzione di ricerca

Start by reading #2207, #2109, and the sample-platform wiring at mod_ci/controllers.py:264-268; compare those with this repository’s GitHub Actions workflows. The proposal calls for running both Linux builds against a small public sample set, reporting output differences without blocking CI, then triaging each difference. The issue asks maintainers to decide where the job and samples should live, so the implementation scope depends on that decision.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

#2207 added two builds so that "both must produce identical output on the sample platform; divergence means a Rust port introduced a behavioral difference". That comparison never got wired up: sample-platform#1122 pointed the platform at the "(with migrations)" builds only (mod_ci/controllers.py:264-268), and no workflow compares the two artifacts. In #2109 you mentioned Rust ports won't be merged until this kind of C-vs-Rust check exists.

I built both variants from master on macOS (same source, only -DDISABLE_RUST differs) and compared them on public samples from https://streams.videolan.org/streams/ts/ with 5 option sets each:

Sample Result
Closed Caption EIA.ts identical
atsc-cea-708-dtvcc-and-cea-608.ts (first 20 MB) 608 identical; the min-rust build writes no 708 file (Rust: 5 cues), both exit 0
CC/wabc-4pm-ota.clip1.ts (US broadcast) 608 identical (40 cues); the min-rust build writes no 708 file (Rust: 42 cues), both exit 0
CC/hevc_cc.ts min-rust build writes nothing (exit 10) although it logs "Total caption blocks received: 762"; Rust extracts 608 + 708

I'd like to build the comparison:

  1. A CI job that runs both Linux artifacts on a small public sample set and reports differences (non-blocking at first).
  2. Triage each difference (fix the C path, or record it as expected).
  3. Then use it as the check for Rust ports.

Two questions before I start:

  • Should this live in this repo's GitHub Actions, or in the sample platform?
  • Where should the samples come from (download from VideoLAN with caching, or the sample platform)?
Lingua principale
C
Stelle
905
Fork
596
Merge medio
4g 5h
PR unite (30g)
33

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di CCExtractor/ccextractor

Tutte le issue di CCExtractor/ccextractor

Issue simili

Altre issue su C

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.