Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

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

Abierto
  • ¿Algo no está bien?
#2,398 1 comentario 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
35/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
c, github-actions, rust
Área
ci-cd, testing-qa

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

#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)?
Lenguaje dominante
C
Estrellas
908
Forks
595
Merge medio
3 d 23 h
PR fusionados (30 d)
32

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de CCExtractor/ccextractor

Todos los issues de CCExtractor/ccextractor

Issues similares

Más issues de C

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.