[deep-report] Scope or budget for agenticworkflows logs' 5-min unfiltered-query timeout floor in deep-report's Step 2
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 2/5
- 预计耗时
- 1 小时以内
- 新手友好度
- 78/100
- Issue 类型
- 文档
- 描述清晰度
- 描述清楚
- 活跃度
- 活跃
- 技术栈
- markdown
调研方向
阅读 .github/workflows/deep-report.md 中的步骤 2，并将其说明与 issue 中描述的超时行为进行比较。更新指南，使用 workflow_name 或较小的 count 限定日志查询范围，或者为未过滤的查询留出足够时间；也可以检查 .github/skills/agentic-workflows/SKILL.md 是否存在相同的问题。当调用方获知如何避免或应对五分钟的最低时长限制时，即为完成。
由索引模型根据 Issue 内容生成。
描述
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
- 主要语言
- Go
- 星标
- 5.4k
- 派生
- 584
- 平均合并
- 3 小时 16 分钟
- 30 天内合并 PR
- 826
环境准备
在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。
- 提供 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
github/gh-aw 的其他 Issue
-
ai-inspected
难度 2/5 1-3 小时 新手友好度 72/100
维护者通常 1 天内回复
-
goroutineresourceleak (81st linter): paren_unwrap_gap across lock/cancel/channel detection, day one未关闭cookie sergo
难度 2/5 1-3 小时 新手友好度 72/100
维护者通常 1 天内回复
-
automation testing
难度 3/5 半天 新手友好度 15/100
维护者通常 1 天内回复
-
agentic-workflows
难度 4/5 1-2 天 新手友好度 22/100
维护者通常 1 天内回复
-
automation testing
难度 1/5 1 小时以内 新手友好度 5/100
维护者通常 1 天内回复
相似的 Issue
-
effort:high model:sonnet phase:3 type:docs
难度 2/5 1-3 小时 新手友好度 68/100
-
难度 2/5 1-3 小时 新手友好度 72/100
OffchainLabs/nitro#4771 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 82/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 65/100
BurntSushi/toml#530 ·
-
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 7 天内回复