Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

[aw] Prompt Optimization reported incomplete result

Abierto
  • ¿Algo no está bien?
#309 1 comentario 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
38/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
docker, github-actions, javascript
Área
ai-infra-agents, ci-cd, infrastructure

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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 · ◷

Lenguaje dominante
JavaScript
Estrellas
6
Forks
1
Merge medio
1 d 5 h
PR fusionados (30 d)
30

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de githubnext/gh-aw-wizard

Todos los issues de githubnext/gh-aw-wizard

Issues similares

Más issues de JavaScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.