Avoid gh /meta probe in firewall issue dispatcher#3596
Conversation
gh /meta probe in firewall issue dispatcher
✅ Coverage Check PassedOverall Coverage
📁 Per-file Coverage Changes (1 files)
Coverage comparison generated by |
There was a problem hiding this comment.
Pull request overview
Updates the firewall issue dispatcher prompt to avoid using the gh CLI for issue prefetching (which can fail due to the CLI’s startup /meta probe on DIFC-proxied runners), and keeps the compiled lock workflow in sync with the source markdown.
Changes:
- Replaced the prompt’s
gh api graphqlexample with RESTcurlcalls toGITHUB_API_URL(search issues + hydrate first 10 comments). - Preserved the JSON shape expected by the prompt (
number,title,body,url,comments.nodes) while avoidinggh. - Regenerated the compiled
.lock.ymlworkflow to reflect the updated markdown prompt.
Show a summary per file
| File | Description |
|---|---|
| .github/workflows/firewall-issue-dispatcher.md | Swaps the prompt’s issue/comment prefetch from gh api graphql to REST curl to avoid /meta probe failures. |
| .github/workflows/firewall-issue-dispatcher.lock.yml | Recompiled lock workflow to match the updated dispatcher markdown prompt. |
Copilot's findings
Tip
Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
- Files reviewed: 2/2 changed files
- Comments generated: 1
| - **No extra reads** — do not open `AGENTS.md`, source files, or any workspace files; all needed context is in the GraphQL response above. | ||
| - **Don't retry without diagnosing** — analyze the error before retrying any failed tool call. No newline at end of file | ||
| - **Don't retry without diagnosing** — analyze the error before retrying any failed tool call. |
Claude Engine Validation ✅
Result: All smoke tests PASS
|
Smoke Test: Copilot BYOK (Offline) Mode ✅PR #3596: Avoid Results:
Note: Running in BYOK offline mode (COPILOT_OFFLINE=true) via api-proxy → api.githubcopilot.com Status: PASS (core BYOK inference validated)
|
Smoke Test Results✅ GitHub MCP: chore(deps): bump dompurify from 3.3.2 to 3.4.5 in /docs-site Overall: FAIL
|
|
Smoke test failed. MCP command not found, SSL connectivity error. Warning Firewall blocked 1 domainThe following domain was blocked by the firewall during workflow execution:
network:
allowed:
- defaults
- "localhost"See Network Configuration for more information.
|
Smoke Test✅ GitHub PR review: Remove unused Warning Firewall blocked 1 domainThe following domain was blocked by the firewall during workflow execution:
network:
allowed:
- defaults
- "registry.npmjs.org"See Network Configuration for more information.
|
Service Connectivity Test Results❌ Redis: Connection timeout (host.docker.internal:6379) Overall: FAIL — Services not reachable from AWF sandbox
|
🏗️ Build Test Suite Results
Overall: 8/8 ecosystems passed — ✅ PASS All build and test operations completed successfully across all ecosystems.
|
The firewall issue dispatcher was still instructing agents to prefetch upstream
awfissues withgh api graphql. On DIFC-proxied runners that fails on the CLI’s startup/metaprobe, preventing the workflow from generating the tracking issue summary and proposed solution.Prompt fetch path
gh api graphqlexample with directcurlcalls toGITHUB_API_URLsearch/issues, then hydrates each issue’s first 10 comments from the REST issue comments endpointnumber,title,body,url,comments.nodes)Proxy-safe auth handling
ghentirely for the prefetch step, so the workflow no longer depends on/metabeing reachableCompiled workflow sync
Example of the new prefetch pattern: