Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[aw] Smoke Gemini failed

Closed
  • Is something wrong?
#8,822 8 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
docker, shell
Domain
ci-cd, devops

Research direction

Start with .github/workflows/smoke-gemini.md, the failed run logs, and the referenced debug.md guidance. Trace why the Gemini harness selects an invalid auth method during the Docker-backed run, then rerun Smoke Gemini and confirm the workflow completes successfully.

Written by the indexing model from the issue text.

Description

agentic-workflows
Workflow Failure

Workflow: Smoke Gemini
Branch: main
Run: https://github.com/github/gh-aw-firewall/actions/runs/35550190483

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

Last agent output:

 api-proxy  Built
 agent  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=3s 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/35550190483
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 28, 2026, 1:17 AM UTC
Dominant language
TypeScript
Stars
149
Forks
77
Avg merge
4h 36m
Merged PRs (30d)
418

Getting set up

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.