[Weekly Summary] Weekly Issue Summary — April 14–20, 2026 #27384
Closed
Replies: 1 comment
-
|
This discussion was automatically closed because it expired on 2026-04-21T15:27:49.907Z.
|
Beta Was this translation helpful? Give feedback.
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.
-
Overview
144 issues were opened in the
github/gh-awrepository over the past 7 days (April 14–20, 2026). Of these, 97 were closed (67% resolution rate) and 47 remain open. Activity was heavily automated — 51 issues were workflow failure reports ([aw] ... failed) and 78 were generated by automated analysis and reporting workflows. 9 issues were opened by human contributors, all of which were resolved within the week.Key Stats
📈 Issue Activity Trends
Weekly Activity Patterns
Issue activity was concentrated in the last 3 days of the period (Apr 18–20), with over 140 issues opened across those days alone. The net change is slightly positive (more opened than closed each day), but the automation machinery is keeping pace — closure rates are high for bot-generated issues.
Resolution Time Analysis
Most issues are resolved within hours to a single day (median ~0.2 days, avg ~0.7 days), which reflects the automated lifecycle of workflow-generated issues. The spike in average resolution time on some days is driven by a small number of longer-lived issues requiring human attention.
🔴 Notable Issues
Workflow Infrastructure Problems
node: command not foundonaw-gpu-runner-T4affecting Daily News and Daily Issues Report Generator (still open)OPENAI_API_KEYcredential missing (still open)Human-Reported Bugs (all resolved ✅)
gh-awself-upgrade fails, leaves extension unrecoverable (ericsciple)gh aw upgradecan't update gh-aw (dsyme)close-issueschema rejects documentedstate-reasonfield (dsyme)create_pull_requestsays "Tool does not exist" (dsyme)dsyme)🏷️ Top Labels This Week
agentic-workflowscookieautomationperformancequick-win/improvementdocumentationoptimizationbug📋 Patterns & Trends
aw-gpu-runner-T4is failing withnode: command not found, a recurring issue across multiple workflows. This is a P1 infrastructure concern.OPENAI_API_KEYcausing consistent 401 failures for Codex-engine workflows.[aw] ... failedissues older than 3 days would significantly reduce tracker noise.Recommendations
node: command not foundonaw-gpu-runner-T4(see #27373)OPENAI_API_KEYfor Codex engine workflows (see #27127)View All 144 Issues (Full List)
node: command not foundon aw-gpu-runner-T4node: command not foundon aw-gpu-runner-T4create_pull_requestsays "Tool does not exist"create_issueReferences: §24674668809
Note
🔒 Integrity filter blocked 11 items
The following items were blocked because they don't meet the GitHub integrity level.
gh aw mcp-serverwrites diagnostic banners tostdout, poisoning the JSON-RPC stream #26920list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".apt-keyis deprecated #27254list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".To allow these resources, lower
min-integrityin your GitHub frontmatter:Beta Was this translation helpful? Give feedback.
All reactions