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

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

Aperta
  • Qualcosa non va?
#924 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
18/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
python
Ambito
ai, backend

Direzione di ricerca

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.

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

Descrizione

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.

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

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.