Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

[aw] Prompt Optimization reported incomplete result

Aperta
  • Qualcosa non va?
#309 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
38/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
docker, github-actions, javascript
Ambito
ai-infra-agents, ci-cd, infrastructure

Direzione di ricerca

Start with .github/workflows/prompt-optimization.md and the agentic-workflows skill, then inspect scripts/prompt-optimizer.mjs and the failed run logs. Trace how the Ollama evaluation server is restored, served, and exposed to the agent container. Done means the workflow can reach the configured models and complete the prompt-optimization evaluation on a rerun.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

agentic-workflows
Workflow Failure

Workflow: Prompt Optimization
Branch: main
Run: https://github.com/githubnext/gh-aw-wizard/actions/runs/37157539293

[!WARNING]
Task Could Not Be Completed: The agent reported that the task could not be performed due to an infrastructure or tool failure.

Reasons:

  • Ollama eval server at (127.0.0.1/redacted) (host-reflected via --enable-host-access --allow-host-ports 11434) is unreachable from the agent sandbox, so no scenario-prompt evaluation or hill-climbing could be run.

    No open PR titled "Prompt optimization:" exists (guard check via gh pr list confirmed only #304, unrelated), so the task proceeded to the hill-climbing loop.

Connectivity diagnosis:

  • curl (127.0.0.1/redacted) and /v1/models`: connection refused.
  • No ollama process, no ~/.ollama cache directory, and no .ollama/GGUF blob files found anywhere on the filesystem searchable from this sandbox — the model-restore/serve steps appear to have run in the GitHub Actions host context, not inside this agent container.
  • Tried all plausible host-access paths: host.docker.internal (DNS SERVFAIL via the container's embedded resolver 127.0.0.11), Docker bridge gateway candidates 172.30.0.1 and 172.17.0.1 (connection refused/timeout), direct squid-proxy CONNECT tunnel to 172.17.0.1:11434 (squid reported "Connection to 172.17.0.1 failed... Connection refused"), squid HTTP-proxy to 172.17.0.1:11434 (403 Access Denied — not in squid's allowlist), and the api-proxy container IP on ports 3128/8080/8000 (connection refused).
  • /etc/hosts inside the agent container only lists the firewall sidecar containers (squid-proxy, api-proxy, cli-proxy, awmg-mcpg/cli-proxy) — no host-gateway entry is present despite the docker-compose audit file showing extra_hosts: host.docker.internal: host-gateway on the squid-proxy and cli-proxy services (not on the agent service itself).
  • No sudo/root capability available to inspect iptables NAT rules or network namespaces further (blocked by no-new-privileges, and inspecting such internals is disallowed by policy regardless).

Net effect: scripts/prompt-optimizer.mjs --evaluate --all-models --eval-url (127.0.0.1/redacted) ... cannot reach either the Qwen2.5-1.5B or SmolLM2-360M proxy model, so no incumbent score, candidate, or hill-climbing step could be measured. No repository files were changed (a pre-existing unrelated modification to .github/skills/optimize-scenario-prompt/SKILL.md was reverted). No PR, review comment, or review 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/37157539293
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 Prompt Optimization · copilot · 152.8 AIC · ◷

Lingua principale
JavaScript
Stelle
6
Fork
1
Merge medio
1g 5h
PR unite (30g)
30

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di githubnext/gh-aw-wizard

Tutte le issue di githubnext/gh-aw-wizard

Issue simili

Altre issue su JavaScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.