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

tooling: gate scripts grew 59x in 7 weeks (592 → 34,804 lines; half the runtime) — freeze, consolidate, budget

Cerrado
#1,275 24 comentarios 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
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
45/100
Tipo de issue
Refactorización
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
c, python, shell

Línea de trabajo

Examine the tools/ directory to list all gate scripts (.sh and .py). For each, check CI history and commit logs to see when it last caught a regression. Compare against structural guarantees like the merge queue (#1264), real wasm build (#1267/#1274), and generated docs (#1269). Start with #1274 as a concrete case to retire or shrink the -m32 gate. Record line counts before and after consolidation.

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

Descripción

area:gates kind:decision

Measured 2026-09-23.

2026-08-01 2026-09-01 now
tools/*.sh/*.py (gates and checkers) 592 lines 6,141 34,804
tests/run_all_tests.sh 3,960 6,104 8,601
src/*.c/*.h (the runtime) 53,153 62,333 71,621

Mean merged PR size: 352 lines (Aug, 52 PRs) → 1,244 (Sep, 68 PRs). Of September's ten largest PRs, six contain 0% product code: #1224 (+7,575, 92% gates/tests/CI), #1226 (+5,130), #1175 (+4,151), #1225 (+4,038), #1164 (+4,045) and #1208 (+3,899, 95%). #1124 was +19,928 with 37% product.

Each gate was built for a real incident. The growth came from each gate then acquiring self-tests, planted faults and checks-of-checks, with nothing ever asking whether a gate still earns its size or has been superseded by something structural. This is the same problem as "have we made CI too hard" (#1264), pointed at our own tooling. Mature languages keep checking machinery small by leaning on structure: a merge queue, building the real target, generating docs from source.

Scope.

  1. Freeze: no new gate script unless it replaces an existing one at equal or smaller size, until item 2 is done. PRs in flight (#1273 and the #1264 contributor-friction PR) are held to this.
  2. Consolidation pass. For every gate in tools/, record its size, the last time it caught a real regression (CI history, or a commit/PR citing it), and whether a structural guarantee now covers it: the merge queue (#1264), the real wasm build (#1267/#1274), generated reference docs (#1269), derived counts (#1264), changelog fragments (#1268). Delete or merge the ones that never fire or are superseded, and record the before/after totals.
  3. Counterweight in the method. The mechanical-gates skill gets a size-budget principle and "prefer a structural guarantee over a script that checks for it". Builder briefs carry a size budget for check machinery.
  4. Visibility: the ratio of gate lines to product lines goes in the daily report, so the trend is seen.

First concrete case: #1274 (retire or shrink the -m32 approximation gate).

Lenguaje dominante
C
Estrellas
3
Forks
7
Merge medio
3 h 58 min
PR fusionados (30 d)
105

Preparar el entorno

Abrir en Codespaces

Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.

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 InauguralSystems/EigenScript

Todos los issues de InauguralSystems/EigenScript

Issues similares

Más issues de C

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.