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

[deep-report] Scope or budget for agenticworkflows logs' 5-min unfiltered-query timeout floor in deep-report's Step 2

Abierto Apto para principiantes
  • ¿Algo no está bien?
#65,727 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
Menos de una hora
Aptitud para principiantes
78/100
Tipo de issue
Documentación
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
markdown
Área
documentation

Línea de trabajo

Lee el paso 2 en .github/workflows/deep-report.md y compara sus instrucciones con el comportamiento del tiempo de espera descrito en el issue. Actualiza las indicaciones para limitar las consultas de logs con un workflow_name o un count pequeño, o para dejar tiempo suficiente para una consulta sin filtros; opcionalmente, comprueba si .github/skills/agentic-workflows/SKILL.md tiene la misma carencia. El trabajo estará terminado cuando se indique a quienes realizan las llamadas cómo evitar o tener en cuenta el límite mínimo de cinco minutos.

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

Descripción

agentic-workflows automation code-quality cookie documentation improvement quick-win task-mining
Description

Every DeepReport cycle that invokes the agenticworkflows MCP logs tool without a workflow_name filter times out client-side before the tool returns — this has recurred across many prior cycles (worked around each time by falling back to in-window discussion reports, never previously filed as its own bug). Root-caused this cycle: pkg/cli/mcp_tools_privileged.go gives unfiltered ("all workflows") logs queries a defaultMCPLogsMinTimeoutMinutesAllWorkflows = 5 minute server-side floor (with defaultMCPLogsToolCount = 100 runs by default), because scanning across every workflow and reading artifacts genuinely takes that long. But deep-report.md's Step 2 ("Gather Workflow Intelligence") gives no guidance to scope the call with a workflow_name or small count, so the agent typically invokes it unscoped and only waits ~50-60s (a typical foreground tool-call budget) — far short of the 5-minute floor the tool itself expects to need.

Reproduced live this cycle: agenticworkflows logs with a -6h window (no workflow filter) returned only MCP keepalive pings for 50s with no final result, identical to the pattern noted in at least 2 prior cycles' briefings (e.g. #65643, and the 2026-09-07T~18:32Z cycle recorded in deep-report's own repo-memory).

Expected Impact

Unblocks DeepReport's own fleet-wide success-rate/token-usage/firewall-activity checks (currently silently skipped nearly every cycle in favor of less-direct discussion-report signals), and documents the real expected latency for any other agent/workflow calling this MCP tool without a workflow filter.

Suggested Fix

Update .github/workflows/deep-report.md Step 2 instructions to either: (a) scope agenticworkflows logs calls with a workflow_name filter or a small count so the call stays within the faster default timeout tier, or (b) explicitly budget for the documented 5-minute floor (e.g. run the call with a longer/background-tolerant invocation) when an unfiltered fleet-wide query is actually wanted. Optionally also note this latency floor in the tool's description/agentic-workflows skill docs so other workflows don't hit the same surprise.

Suggested Agent

deep-report itself (prompt/doc change only — no Go code change needed) or a documentation-focused agent via .github/skills/agentic-workflows/SKILL.md.

Estimated Effort

Quick (< 1 hour) — prompt/doc wording change.

Data Source

DeepReport Intelligence Briefing — 2026-10-05 cycle (incremental, baseline #65643). Root cause confirmed via direct read of pkg/cli/mcp_tools_privileged.go (defaultMCPLogsMinTimeoutMinutesAllWorkflows, defaultMCPLogsToolCount, effectiveMCPLogsToolTimeoutMinutes) cross-referenced against .github/workflows/deep-report.md's Step 2 prompt text (no scoping guidance present) and this cycle's live reproduction.

Generated by 🔬 Deep Report · claude · agent · 216.9 AIC · ⌖ 8.14 AIC · ⊞ 7.1K · ◷

  • expires on Oct 6, 2026, 5:18 PM UTC-08:00
Lenguaje dominante
Go
Estrellas
5.4k
Forks
576
Merge medio
8 h 46 min
PR fusionados (30 d)
753

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.