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

Captured-pair gates: score fresh runs against an oracle-side-only top-K golden instead of the self-anchor

Abierto
  • ¿Algo no está bien?
#3,160 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
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
35/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
bash, cpp
Área
backend, testing-qa

Línea de trabajo

Comienza con .agents/specs/tenstorrent-keepquant.md y scripts/qwen35-q4km-neartie-gap.sh, y después revisa el flujo de verified-pair y #2959. Define el cambio del checker con su propia spec, demuestra un re-roll de ULP con un estado rojo previo y proporciona evidencia de mutación de que una divergencia real sigue fallando antes del review.

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

Descripción

Row: BACKEND-TENSTORRENT-KEEPQUANT

Problem

The captured-pair gates (the qwen3.5 Q4_K_M TT vehicle today; the same
ladder shape in the qwen3/mistral gates) pin two functions of OUR engine's
numerics: the exact ids anchor (self-match REQUIRE) and a per-capture
teacher-forced gap golden. Every ULP-level shift — a tt-metal pin bump, a
kernel change — re-rolls the ~51/256 near-tie cells and turns the gate red,
forcing a golden refresh. The refresh itself is where the process failed on
2026-09-12: an off-recipe re-derivation wrote f32-grain gaps that
manufactured four band violations and nearly drove a kNearTieMnats
widening (recorded in .agents/specs/tenstorrent-keepquant.md, Evidence).
The pinned-recipe truth was max gap 250 mnats, 0 cells above band — the
engine was fine; the refresh path was not.

Proposed shape

Commit an oracle-side-only golden: per prompt cell, the pinned oracle's
top-K logprobs under the ORACLE's own greedy prefix — stable under our code
changes, so it never re-captures for engine-side reasons. The gate scores
the fresh engine run against the committed top-K up to the first
divergence and fails only a confident divergence (gap above band, or our
token outside top-K). Near-tie flips pass with a recorded margin. The
self-anchor exact REQUIRE becomes an advisory MESSAGE recording the
re-roll. At the decision cell this is exactly the bar the gap script's own
header declares ("is our token, given our exact prefix, one the oracle
cannot confidently separate"); post-flip cascade cells are cross-context
and uninformative today anyway.

Why not now

The verified pair plus the provenance-hardened re-derivation path
(scripts/qwen35-q4km-neartie-gap.sh) lands in #2959's flow. This
redesign is a semantic checker change: it needs its own spec, a
red-before demonstration (a ULP re-roll failing today's anchor),
mutation evidence that a real divergence still fails, and fresh review.

Lenguaje dominante
C++
Estrellas
423
Forks
53
Merge medio
1 d 7 h
PR fusionados (30 d)
382

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 mudler/vllm.cpp

Todos los issues de mudler/vllm.cpp

Issues similares

Más issues de C++

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.