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

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

Aperta
  • Qualcosa non va?
#917 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
25/100
Tipo di issue
Refactoring
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
python
Ambito
ci-cd, tooling

Direzione di ricerca

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.

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

Descrizione

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.

Lingua principale
Python
Stelle
9
Fork
1
Merge medio
4h 3m
PR unite (30g)
3

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

Tutte le issue di HodeTech/ForgeLM

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.