Skip to content

[deep-report] Fix recurring 60s timeout in gh-aw logs MCP tool degrading audit datasets #45510

Description

@github-actions

Description

The gh-aw logs MCP tool hits its 60s transport timeout (context deadline exceeded) mid-download on the 07-11, 07-13, and 07-14 audit runs. As a result the Safe Output Health report (#45381) and the GitHub API Consumption report (#45454) both ran on partial datasets — safe-output-health fell back to on-disk run_summary.json files, and api-consumption explicitly labeled its totals a lower bound (only 101 of the last-24h runs finished downloading). Add pagination/streaming or a higher/ configurable timeout, or chunk the download, so audits get complete data.

Expected Impact

Restores full-fidelity audit datasets across multiple daily reporting workflows, eliminating a 3+ day recurring 'partial dataset' caveat that undermines confidence in fleet metrics.

Suggested Agent

New Agent (tooling/infra) or a maintainer — touches the gh-aw MCP server logs implementation.

Estimated Effort

Medium (1-4 hours)

Data Source

DeepReport analysis 2026-07-14; source reports [safe-output-health] #45381, [api-consumption] #45454.

Generated by 🔬 Deep Report · 260.7 AIC · ⌖ 17.6 AIC · ⊞ 10K ·

  • expires on Jul 16, 2026, 7:23 AM UTC-08:00

Metadata

Metadata

Type

No type

Fields

No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions