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

Add gate on full-sweep / fail-fast runs to prevent wasted compute

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

Los mantenedores suelen responder en 1 día

@adibarra ya está trabajando en esto.

Desde el 6/7/2026.

Evaluación

Este issue todavía no se ha evaluado.

Descripción

dev velocity enhancement p1

Summary

Add a gate on compute-heavy sweep runs (full-sweep-fail-fast, full-sweep, non-canary-full-sweep-enabled, etc.) to prevent obviously-wrong / wasteful runs from consuming compute before they start.

Motivation

Compute-intensive sweeps are expensive, and there is currently no guardrail to stop a run that is clearly misconfigured or violating known bad patterns. This wastes runner time, increases queue times, and blocks other engineers' work. Stopping wasted compute here is P1.

Related: this ties into the broader InferenceX compute-improvement effort of stopping people from sweeping trtllm/atom before submitting/validating vllm/sglang, which increases queue time and blocks vllm/sglang work (ATOM engineers wasting other AMD engineers' time).

Approaches discussed

  • FORBIDDEN_HACK.md allow/deny list (preferred starting point): Maintain a simple markdown file of forbidden patterns/hacks that we append to as needed. A gate reads it and denies a run when a known bad pattern is detected. Cheap, deterministic, low false-positive risk.
    • Run this gate only on fail-fast / canary runs (not every run) to limit overhead.
  • LLM-based gate (fallback / later): Call an LLM to evaluate whether a run should be denied.
    • Pros: catches novel bad patterns.
    • Cons: risk of false positives; cost. If pursued, use a cheaper model (e.g. Haiku / Sonnet 5 / fable5) rather than an expensive review model. Estimated ~$1–2 per fable call, cheaper than the ~$20/review Claude enterprise PR code review.

Notes

  • The CODEOWNER sign-off review is considered valuable and should stay.
  • Keep the gate scoped to fail-fast / canary runs initially to control cost.

Scope

Start with the FORBIDDEN_HACK.md + gate on fail-fast/canary runs. Evaluate an LLM-based check later if needed.

Lenguaje dominante
Python
Estrellas
1.9k
Forks
343
Merge medio
2 d 40 min
PR fusionados (30 d)
431

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 SemiAnalysisAI/InferenceX

Todos los issues de SemiAnalysisAI/InferenceX

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.