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

Implement `output.cost_tracking` (per-GPU rates, alert / halt thresholds, audit and webhook events) — or retire the promise

Abierto
  • ¿Algo no está bien?
#924 0 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
18/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
python
Área
ai, backend

Línea de trabajo

Start with the deferral row at docs/roadmap/risks-and-decisions.md:94 and the GPU-cost manual pages (EN and TR) that advertise output.cost_tracking. Confirm that ForgeConfig in forgelm/ has only the scalar training.gpu_cost_per_hour field. The maintainers have not chosen a path, so first ask whether to build the block or drop the promise. Done means either the schema, audit event, webhook event and EN/TR docs exist, or the manual and roadmap drop the promise. In both cases the row leaves the deferral table and the CHANGELOG names F-PR29-A2-04.

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

Descripción

area: config severity: medium source: roadmap wave: 3

Deferred work · F-PR29-A2-04 · severity Medium · cost ~1 day · recorded in docs/roadmap/risks-and-decisions.md:94

Summary

The GPU-cost manual (EN + TR) advertises an output.cost_tracking block with per-GPU rates, a currency and alert / halt thresholds, but ForgeConfig has no such field; only the scalar training.gpu_cost_per_hour exists. The PR #29 review deferred it because it needs a CostTrackingConfig model, an audit event when a threshold is crossed and a webhook lifecycle event (which extends the published webhook vocabulary). The documentation issues only correct the pages, so the build-or-drop decision is still open.

Condition or budget

None recorded (the row still names v0.6.x).

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

No cost_tracking or CostTrackingConfig exists in forgelm/; the manual labels its examples as forward-looking placeholders.

Related

#428, #241, #429 and #444 correct the cost documentation; none asks for the implementation.

Acceptance criteria

  • Either the block exists (schema, audit event, webhook event, EN/TR docs) or the manual and the roadmap drop the promise and the row is closed with that reason.
  • 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
11 h 8 min
PR fusionados (30 d)
10

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.