DeepReport Intelligence Briefing - 2026-07-16 #46029
Closed
Replies: 1 comment
|
This discussion has been marked as outdated by Deep Report. A newer discussion is available at Discussion #46271. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
🔍 Executive Summary
The gh-aw fleet is healthy but read-only, and one workflow now dominates both failure and cost: safe-output jobs are 100% clean for a 4th consecutive day (14/14 today, 0 write actuations), yet Smoke CI's copilot-CLI 0-turn failure has grown from 26.6% → 42.3% of the 24h REST-API quota (36,567 calls across 25 runs, all non-success) while remaining 0% success and unfixed since 06-30 (#45429/#45931). The top finding: one driver root-cause retires the entire failure surface (fleet is 81.8% → 90.0% success ex-Smoke CI) and the #1 quota burner simultaneously. Bright spot: the 6-week Copilot "provenance inversion" broke today — CI-gate workflow-types recorded real completions for the first time (38%, a 9-day high). Urgent action: root-cause the copilot-CLI startup driver; the
logsMCP tool 120s timeout continues to force partial datasets on three audits daily.🚨 Top 5 Findings
logsMCP tool 120s timeout keeps degrading fleet metrics. API Consumption (102 of ~270 run dirs), the workflow audit (100 of 225), and prior windows all fall back to partial datasets — daily health numbers are computed on incomplete data.push_to_pull_request_branchhard-fails withdubious ownership(bridge runs as a different user/HOME than the container, sogit config safe.directorynever reaches it). Latent since 06-26 only because the fleet is read-only — filed a tracking issue this run.✅ Actionable Agentic Tasks
Seven new GitHub issues were filed — each dedup-checked against open + closed issues; none duplicate the fleet's same-day self-filed batch or yesterday's items:
downloadArtifactsOptionsstruct + delete 2//nolint:excessivefuncparams9-param suppressions (logs_run_processor.go:104,update_actions.go:606, 4 siblings inlogs_download.go) — Quick — from [repository-quality].buildCopilotStepEnv(3 bools) andGenerateNpmInstallStepsWithScope(4 bools) — Quick — from [repository-quality].copilot_events_jsonl.go/token_usage.go(Typist Cluster 8) — Medium.AccessLogSummary/FirewallLogSummaryinlogs_report_firewall.go(Typist Cluster 4) — Medium.DomainAnalysis/FirewallAnalysis(access_log.go/firewall_log.go, Typist Cluster 5) — Medium.Process Safe Outputsstep stdout on failure so safe-output hardfails are diagnosable from artifacts — Medium — from [safe-output-health] (its top recurring observability ask).push_to_pull_request_branchdubious-ownership hardfail (bridgesafe.directory/ user+HOME alignment) — Medium — from [safe-output-health] watch-list item 1.View Full Details — metrics snapshot & watch items (deliberately NOT re-filed)
Watch items (already tracked or upstream — deliberately NOT re-filed):
logsMCP 120s timeout — degrading 3+ audits daily via partial datasets.gh-aw-detection) — relates to CLOSED [deep-report] Add gh-aw-detection: true to 5 flagged audit/analysis workflows #45284; watched, not re-filed.actions_listMCP tool ignoresperPage(returns 30 of 330) — page defensively; likely upstream.References:
All reactions