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

Internal mypy debt has grown past its recorded budget: 108 errors in 36 files against 106 in 35

Abierto
  • ¿Algo no está bien?
#917 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
25/100
Tipo de issue
Refactorización
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
python
Área
ci-cd, tooling

Línea de trabajo

Start by running ./.venv/bin/python -m mypy --ignore-missing-imports forgelm/ to list the 108 errors across 36 files, and read the deferral row at docs/roadmap/risks-and-decisions.md:262. Choose between fixing enough errors to get back to 106 or below, or re-baselining with a written reason. Done means the count is within budget, a CI step fails on growth past the budget, and the row is removed with its ID named in the CHANGELOG.

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

Descripción

area: dev-tooling severity: low source: roadmap wave: 4

Deferred work · F-W20260729-OPS-23-internal · severity Low · cost ~1-2 days · recorded in docs/roadmap/risks-and-decisions.md:262

Summary

Phase 16 S1 wired the public-surface mypy --strict gate and recorded the package-wide typing debt as a budget instead of a blocker: 106 errors across 35 files, measured with mypy 1.20.2 and ./.venv/bin/python -m mypy --ignore-missing-imports forgelm/, with growth past 106 named as the signal to act. That signal has fired, and nothing in CI enforces the budget, which is why the growth went unnoticed.

Condition or budget

"Growth past 106 is the signal to act" — met: the recorded command reports 108 errors in 36 files on 2026-10-09.

State today (re-checked 2026-10-09)

Re-measured on development with the recorded command and mypy 1.20.2: Found 108 errors in 36 files (checked 104 source files).

Related

#748 corrects the stale "47" in the Phase 16 plan (documentation only).

Acceptance criteria

  • The count is back to 106 or below, or the budget is re-baselined with a written reason.
  • Growth past the budget fails CI (a ratchet), so the next increase is caught when it happens.
  • The row is removed from the deferral table and the CHANGELOG names its ID (the table's removal contract).

Recorded in docs/roadmap/risks-and-decisions.md (read at f94595f) and re-checked against the code on 2026-10-09. The row leaves that table only when the fix is on main, the CHANGELOG names its ID and any promised guard exists.

Lenguaje dominante
Python
Estrellas
9
Forks
1
Merge medio
8 h 10 min
PR fusionados (30 d)
5

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 HodeTech/ForgeLM

Todos los issues de HodeTech/ForgeLM

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.