[cli-tools-test] [CLI exploratory testing] Windows deprecated missing-tool key fails strict dry-run gate

Abierto Apto para principiantes
  • ¿Algo no está bien?
#74,755 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
2/5
Tiempo estimado
1-3 horas
Aptitud para principiantes
70/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
github-actions, go
Área
ci-cd

Línea de trabajo

Lee .github/workflows/windows.md alrededor de la línea 54 y comprueba cómo configuran las salidas seguras los ejemplos de workflows de confianza. Migra la clave obsoleta missing-tool a report-missing-tool; después, compila el workflow de Windows con ajustes estrictos de ejecución en seco y revisa el archivo windows.lock.yml regenerado. La tarea estará terminada cuando pase la barrera de advertencias del lote y el archivo lock refleje el workflow actualizado.

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

Descripción

automation cli-tools testing
Overview

Bounded testing on 2026-11-04 found that .github/workflows/windows.md:54 uses the deprecated missing-tool safe-output key. Its strict dry-run compile emits a lock but fails the overall warning gate. Severity: Low; observed once. This is a repository workflow compatibility issue, not evidence that the safeguard should be weakened.

Reproduction
  1. On github/gh-aw, invoke agenticworkflows MCP compile with workflows=[windows], dry_run=true, strict=true.
  2. Inspect both workflow and batch results.
  3. The workflow result is valid and identifies windows.lock.yml, but the compiler batch is invalid and dry_run.gate is failed.

Expected: the maintained trusted sample uses current settings and passes the strict gate. Actual diagnostic: The missing-tool safe-output key is deprecated. Use report-missing-tool instead.

Proposed correction: migrate the setting through normal workflow maintenance, then compile and review the regenerated lock. No workflow source was edited by this tester.

Diagnostics and bounded coverage

Passed checks

  • Discovery returned 356 workflows, all marked compiled. Sampled triggers and imports matched the selected sources; freshness was not independently established.
  • Five logs queries, always count=3: last day; daily-workflow-security-model over seven days; copilot engine over one day; nonexistent-workflow-xyz; future date 2099-01-01. Exposed JSON summaries were readable. Nonempty results had at most three runs and consistent IDs, workflow names, engines, statuses and timestamps. Unknown workflow returned actionable guidance; future date returned zero runs. Count-limited results warned about partial coverage.
  • Two completed-run audits: failed Daily Workflow Security Model and successful PR Finisher. Metadata agreed with logs. Reports exposed job timing, metrics and safe-output summaries; the success sample exposed bash and safeoutputs.noop calls, MCP health, and 24 network requests. Its noop described unfinished task work, so workflow success is not task completion. Neither sample created GitHub resources. Invalid audit ID 0 returned clear guidance.
  • Windows emitted a local lock with frontmatter/body hashes, strict/dry-run metadata, expected job sections and staged safe outputs; ShellCheck passed with zero added findings. This was structural inspection, not independent complete Actions validation.
  • Logs took approximately 7.5–9.7 seconds for nonempty queries and 1.5 seconds for the future date. Audits took 11.0 and 9.4 seconds. Compiles took 0.9–2.7 seconds. These are single observations.

Observed problems

Windows failed the batch warning gate on the deprecated key. A per-workflow valid result must not be interpreted as an overall gate pass. The tool also warned that cached model inventory may be stale.

Blocked or unfinished required checks

All three targeted compiles used dry_run=true and strict=true; zero passed the overall gate. Archie was rejected for pre-agent steps and custom MCP servers. Daily Workflow Security Model was rejected for custom steps. These safeguard denials were not retried or worked around. Passing complex/import compilation, corresponding generated-lock inspection, and compile-to-existing-run integration remain unverified. The failed existing run used SHA f3dc4385203cb61f4ebc410546ee91822538e884; it does not validate a newly generated lock.

Not tested (expected exclusion)

  • Malformed YAML, invalid tool configuration and missing imports: synthetic fixtures prohibited.
  • Private raw logs, raw directory structure and independent artifact completeness: outside scope.
  • Execution of newly compiled locks: dispatch prohibited.
  • Historical/retention and in-progress audit variants: outside the two completed-run sample.
  • Redundant date variants and incremental recompilation: optional variants omitted after failed compile gates.
  • Created-resource links and failed sub-agent attribution: not exercised by these samples.
Next actions

Migrate the Windows setting and review which trusted samples satisfy the existing safeguards. Required compile coverage is incomplete and is being reported separately. No locks were published, pushed or executed. This sample does not establish repository-wide CLI health.

References:

Generated by 🧪 Daily Cli Tools Tester · codex · gpt60 · ~155 AIC · ⌖ ~57 AIC · ⊞ 21.2K · ◷

  • expires on Nov 10, 2026, 9:23 PM UTC-08:00
Lenguaje dominante
Go
Estrellas
5.6k
Forks
615
Merge medio
5 h 36 min
PR fusionados (30 d)
805

Preparar el entorno

Abrir en Codespaces

Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.

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 github/gh-aw

Todos los issues de github/gh-aw

Issues similares

Más issues de Go

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.