githubnext / githubnext/gh-aw-wizard
[aw] Prompt Optimization reported incomplete result
- Dominant language
- JavaScript
- Stars
- 3
- Forks
- 0
- Avg merge
- 3h 8m
- Merged PRs (30d)
- 244
Description
### Workflow Failure
**Workflow:** [Prompt Optimization](https://github.com/githubnext/gh-aw-wizard/blob/main/.github/workflows/prompt-optimization.md)
**Branch:** main
**Run:** https://github.com/githubnext/gh-aw-wizard/actions/runs/33992622296
> [!WARNING]
> **Task Could Not Be Completed**: The agent reported that the task could not be performed due to an infrastructure or tool failure.
**Reasons:**
- The Ollama OpenAI-compatible server at (127.0.0.1/redacted) required for the prompt-optimizer evaluation loop is not running/reachable, despite the task description stating it was pre-started.
Checks performed: (1) `curl (127.0.0.1/redacted) returned "Connection refused". (2) `ps aux | grep -i ollama` found no ollama process. (3) `which ollama` returned empty (binary not on PATH). (4) `ss -tlnp`/`netstat -tlnp` showed no listener on port 11434. (5) No ollama log files found on disk.
No open PR titled "Prompt optimization:" exists (checked via `gh pr list --state open`), so the existing-PR-review guard did not apply either.
Since neither --evaluate nor --score can run without the eval server, I could not measure a baseline or any candidate, and per the task instructions I must never claim an improvement the harness did not measure. No repository files were changed. No PR or review comment was created.
This is a structured incompletion signal (`report_incomplete`), not a real task outcome. Any other safe outputs emitted alongside this signal (e.g., comments) describe the failure state, not a completed review or action.
### 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/githubnext/gh-aw-wizard/actions/runs/33992622296
````
Manually invoke the agent
Debug this workflow failure using your favorite Agent CLI and the `agentic-workflows` prompt.
- Start your agent
- Load the `agentic-workflows` skill from `.github/skills/agentic-workflows/SKILL.md` or
- Type `debug the agentic workflow prompt-optimization failure in https://github.com/githubnext/gh-aw-wizard/actions/runs/33992622296`
> [!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:
> ```yaml
> safe-outputs:
> report-failure-as-issue: false
> ```
>
>
> Generated from [Prompt Optimization](https://github.com/githubnext/gh-aw-wizard/actions/runs/33992622296) · copilot · 23 AIC · [◷](https://github.com/search?q=repo%3Agithubnext%2Fgh-aw-wizard+is%3Aissue+%22gh-aw-workflow-id%3A+prompt-optimization%22&type=issues)
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with .github/workflows/prompt-optimization.md and inspect the failed run linked in the issue. Read the agentic-workflows skill or debug.md, then investigate why the Ollama server at the expected endpoint is unavailable during the workflow. Done means the evaluation loop can run and produce a measured result rather than report_incomplete.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, ollama
- Domain
- ai-infra-agents, ci-cd, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100