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

CTL-010 prints 'no bypasses detected' in the same run that WARNs about N bypasses — the PASS message asserts more than it measures

Abierto Apto para principiantes
  • ¿Algo no está bien?
#49 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
2/5
Tiempo estimado
1-3 horas
Aptitud para principiantes
76/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
shell, yaml
Área
cli, devtools

Línea de trabajo

Empieza en agents/audit/audit.sh alrededor de las líneas 4998–5017, donde CTL-010 formatea su mensaje PASS, e inspecciona la prueba o las comprobaciones de auditoría relevantes para ese control. Ejecuta fw audit para comparar el mensaje con el recuento de bypasses; estará listo cuando CTL-010 delimite claramente su afirmación al registro de git --no-verify sin dar a entender que no existen otros bypasses.

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

Descripción

A single fw audit run prints both of these, within a few lines of each other:

[WARN] Gate-bypass log: 11 safety bypasses in last 7 days
[PASS] CTL-010: Bypass log exists but empty (no bypasses detected)

Reproduced live on framework 1.6.769 on 2026-09-21. The count has read 7, 9 and 11 across
separate runs; the shape is stable, only the number moves.

It is not a contradiction, and that is the problem

The two lines read different files:

  • CTL-010 reads .context/bypass-log.yaml — the git --no-verify log, which really is
    bypasses: [].
  • The WARN reads .context/working/.gate-bypass-log.yaml — framework gate bypasses
    (FW_SWITCH_FOCUS, FW_ALLOW_HOST_SIGNED_RAIL, and so on), which had 18 entries.

So both statements are true about their own source. The defect is that CTL-010's PASS
message asserts more than CTL-010 measures. agents/audit/audit.sh:4998-5017 hard-codes
the string "no bypasses detected" with no scope qualifier. An operator scanning an audit
report sees an unqualified all-clear sitting next to a warning about eleven bypasses, and
has to open the source to learn that the two are talking about different logs.

Two adjacent notes
  • The second log, .context/working/.gate-bypass-log.yaml, is malformed YAML —
    yaml.safe_load raises a ParserError. So the file the WARN counts cannot be parsed by a
    YAML reader, while the file CTL-010 calls empty parses fine. Tracked downstream, but it
    means the unqualified PASS is masking a corrupt sibling, not just a narrower one.
  • This is the same shape as issue #45: a declaration the framework makes about itself,
    written in one place and read in another, that nothing re-evaluates at the point of use.
Suggested fix

One line: have CTL-010 name its scope — "no git --no-verify bypasses" rather than "no
bypasses detected". If the two logs are meant to be one surface, merging them is the
larger fix; qualifying the sentence is the cheap one and removes the false all-clear
immediately.

Filed from project 1409-sprind under T-1133 (observation-inbox triage), from OBS-026,
re-measured against a live audit run rather than carried from the original capture.

Lenguaje dominante
Shell
Estrellas
16
Forks
6
Merge medio
6 h 24 min
PR fusionados (30 d)
5

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 DimitriGeelen/agentic-engineering-framework

Todos los issues de DimitriGeelen/agentic-engineering-framework

Issues similares

Más issues de Shell/Bash

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.