-
Notifications
You must be signed in to change notification settings - Fork 18
[aw] Firewall Issue Dispatcher failed #1785
Copy link
Copy link
Open
Labels
Description
Workflow Failure
Workflow: Firewall Issue Dispatcher
Branch: main
Run: https://github.com/github/gh-aw-firewall/actions/runs/24122130637
copilot engine terminated unexpectedly.
Last agent output:
└ [{"author_association":"CONTRIBUTOR","body":"## Summary\nA same-UID process c...
✗ issue_read (MCP: github) · issue_number: 1786, method: "get", owner: "github", repo: "gh-aw-firew…
└ MCP server 'github': McpError: MCP error 0: calling "tools/call": failed to get issue: GET
https://api.github.com/repos/github/gh-aw-firewall/issues/1786: 404 Not Found []
● list_issues (MCP: github) · direction: "DESC", orderBy: "CREATED_AT", owner: "github", perPage: 1…
└ Output too large to read at once (40.8 KB). Saved to: /tmp/1775631963344-copi...
● List issue numbers and titles (shell)
│ cat /tmp/1775631963344-copilot-tool-output-k080go.txt | python3 -c "import json,sys;
│ issues=json.load(sys.stdin); [print(i['number'], i['title'][:80]) for i in issues]"
└ 11 lines...
Action Required
Assign this issue to Copilot using the agentic-workflows sub-agent to automatically debug and fix the workflow failure.
Debug with any coding agent
Use this prompt with any coding agent (GitHub Copilot, Claude, Gemini, etc.):
Debug the agentic workflow failure using https://raw.githubusercontent.com/github/gh-aw/main/debug.md
The failed workflow run is at https://github.com/github/gh-aw-firewall/actions/runs/24122130637
Manually invoke the agent
Debug this workflow failure using your favorite Agent CLI and the agentic-workflows prompt.
- Start your agent
- Load the
agentic-workflowsprompt from.github/agents/agentic-workflows.agent.mdor https://github.com/github/gh-aw/blob/main/.github/agents/agentic-workflows.agent.md - Type
debug the agentic workflow firewall-issue-dispatcher failure in https://github.com/github/gh-aw-firewall/actions/runs/24122130637
Tip
Stop reporting this workflow as a failure
To stop a workflow from creating failure issues, set report-failure-as-issue: false in its frontmatter:
safe-outputs:
report-failure-as-issue: falseGenerated from Firewall Issue Dispatcher · ◷
- expires on Apr 15, 2026, 7:14 AM UTC
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
Type
Fields
Give feedbackNo fields configured for issues without a type.