[aw] Smoke Gemini failed

Open
#8,803 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
bash, docker, github-actions
Domain
ai, ci-cd, devops

Research direction

Start with .github/workflows/smoke-gemini.md at the 8802 revision and the failed run 35525803208. Read debug.md or .github/skills/agentic-workflows/SKILL.md, then trace the Gemini harness output and the selected authentication method. Done means the Smoke Gemini workflow completes without the engine terminating with exit code 41.

Written by the indexing model from the issue text.

Description

agentic-workflows cascade-suspected
Workflow Failure

Workflow: Smoke Gemini
Branch: nvx-phase-3-opt-in-backend
Run: https://github.com/github/gh-aw-firewall/actions/runs/35525803208
Pull Request: #8802

[!WARNING]
Engine Failure: The gemini engine terminated unexpectedly.

Last agent output:

 agent  Built
 api-proxy  Built
[gemini-harness] attempt 1: spawning: bash gemini
[gemini-harness] attempt 1: process started (pid=347)
YOLO mode is enabled. All tool calls will be automatically approved.
Invalid auth method selected.
[gemini-harness] attempt 1: process exit event exitCode=41
[gemini-harness] attempt 1: process closed exitCode=41 duration=2s stdout=0B stderr=99B hasOutput=true
Run 'docker run --help' for more information
Run 'docker run --help' for more information
Action Required

Assign this issue to an agent to debug and fix the issue.

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/35525803208
Manually invoke the agent

Debug this workflow failure using your favorite Agent CLI and the agentic-workflows prompt.

[!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: false

Generated from Smoke Gemini · ◷

  • expires on Sep 27, 2026, 5:29 PM UTC
Dominant language
TypeScript
Stars
145
Forks
63
Avg merge
5h 55m
Merged PRs (30d)
226

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from github/gh-aw-firewall

All issues in github/gh-aw-firewall

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.