-
Notifications
You must be signed in to change notification settings - Fork 36
Enable firewall (AWF) for smoke-copilot and smoke-copilot-playwright workflows #6901
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
…workflows Co-authored-by: Mossaka <5447827+Mossaka@users.noreply.github.com>
|
📰 DEVELOPING STORY: Smoke Copilot reports failed. Our correspondents are investigating the incident... |
|
🎉 Yo ho ho! Changeset Generator found the treasure and completed successfully! ⚓💰 |
|
🤖 DIAGNOSTIC COMPLETE: Smoke Copilot No Firewall STATUS: ALL_UNITS_OPERATIONAL. MISSION_SUCCESS. |
|
💀 Blimey! Smoke Copilot Safe Inputs failed and walked the plank! No treasure today, matey! ☠️ |
|
🎬 THE END — Smoke Claude MISSION: ACCOMPLISHED! The hero saves the day! ✨ |
|
✨ The prophecy is fulfilled... Smoke Codex has completed its mystical journey. The stars align. 🌟 |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
I analyzed the CI failures at https://github.com/githubnext/gh-aw/actions/runs/20355160413/job/58488921366 and https://github.com/githubnext/gh-aw/actions/runs/20355160424/job/58488922722. Root cause: The Copilot CLI fails with "Directory does not exist or cannot be accessed: /home/runner/work/gh-aw/gh-aw" when running inside the AWF container. Analysis:
Possible causes:
Recommendation: This appears to be an AWF/Copilot CLI compatibility issue, not a problem with the workflow configuration. The changes made (switching |
|
@copilot merge main |
…ile lock files Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
|
📰 VERDICT: Smoke Copilot has concluded. All systems operational. This is a developing story. 🎤 |
|
🎉 Yo ho ho! Changeset Generator found the treasure and completed successfully! ⚓💰 |
|
🤖 DIAGNOSTIC COMPLETE: Smoke Copilot No Firewall STATUS: ALL_UNITS_OPERATIONAL. MISSION_SUCCESS. |
|
🎬 THE END — Smoke Claude MISSION: ACCOMPLISHED! The hero saves the day! ✨ |
|
🎉 Yo ho ho! Smoke Copilot Safe Inputs found the treasure and completed successfully! ⚓💰 |
|
✨ The prophecy is fulfilled... Smoke Codex has completed its mystical journey. The stars align. 🌟 |
Smoke Test ResultsLast 2 Merged PRs:
Test Results:
Status: PASS PR Author:
|
|
Last merged PRs: "Bump gh-aw-firewall version from v0.6.0 to v0.7.0", "Disable
|
Smoke Test Results: PASS ✅Last 2 Merged PRs:
Test Results:
Overall Status: PASS
|
Smoke Test Results for Claude (Run 20359671810)Last 2 Merged PRs:
Test Results: Overall Status: PASS (5/6 tests passed, gh CLI failure is environment limitation)
|
Smoke Test Results - Copilot EngineLast 2 Merged PRs: ❌ (GitHub MCP/API auth failed) Overall Status: ❌ FAIL - 2/5 tests passed Environment lacks GitHub auth token, safeinputs-gh tool, and Serena MCP access.
|
sandbox.agent: falsetosandbox.agent: awffor smoke-copilot.mdsandbox.agent: falsetosandbox.agent: awffor smoke-copilot-playwright.mdCI Failure Analysis:
Both smoke-copilot and smoke-copilot-playwright workflows fail with:
Root cause: The Copilot CLI's
--add-dirvalidation fails inside the AWF container, even though the workspace is correctly mounted. This appears to be an AWF/Copilot CLI compatibility issue that requires investigation in the gh-aw-firewall repository.Original prompt
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.