[aw] Prompt Optimization reported incomplete result
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 42/100
- Issue 类型
- 缺陷
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- github-actions, ollama
- 领域
- devops, infrastructure
调研方向
Start with .github/workflows/prompt-optimization.lock.yml around the Ollama setup and model pull steps cited in the issue, then read .github/workflows/prompt-optimization.md and the linked workflow run. Trace why Ollama and its models are unavailable inside the agent sandbox and check how the workflow exposes the service and network access. Done when the workflow can run its optimization evaluation and report a result.
由索引模型根据 Issue 内容生成。
描述
Workflow Failure
Workflow: Prompt Optimization
Branch: main
Run: https://github.com/githubnext/gh-aw-wizard/actions/runs/38310132548
[!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 proxy-model infrastructure this task depends on is not reachable from the agent sandbox, so no hill-climbing evaluation could be run.
Pre-flight check: searched for an open PR titled "Prompt optimization:" via
gh pr list— none exists, so optimization should have proceeded.
Infrastructure failure: (127.0.0.1/redacted) (the Ollama server the task says is already running) was not listening in this sandbox — curl returned connection refused (exit 7) from the start, before I touched anything. No ollamaprocess was running and~/.ollama` did not exist (no cached blobs/models restored into this container).
Recovery attempt 1: Located the ollama binary at /opt/hostedtoolcache/ollama/0.33.2/x64/ollama and started ollama serve myself in-container. It came up fine (Listening on 127.0.0.1:11434, total blobs: 0), confirming no model cache was present here.
Recovery attempt 2: Tried ollama pull hf.co/bartowski/Qwen2.5-1.5B-Instruct-GGUF:Q4_K_M to populate it locally. The outbound firewall (squid proxy) returned 403 Forbidden for both hf.co and huggingface.co — these hosts are not in this workflow's allowed egress domains, so the model cannot be fetched from inside the agent sandbox. Also probed likely host-gateway addresses (docker bridge gateway, 172.30.0.1, host.docker.internal) in case the actual GitHub Actions job (which per the lock.yml does actions/cache restore + ai-action/setup-ollama + ollama pull with full default/node network access) had a reachable instance; none responded, and allow-host-ports: [11434] did not expose any live host-side listener to this container.
I stopped my own locally-started ollama serve process and reverted an unrelated auto-generated metadata diff in .github/skills/optimize-scenario-prompt/SKILL.md that appeared during skill restoration, so the working tree is clean (git status --porcelain empty). No candidate was measured, no files were changed, and no pull request or review comment was created.
Likely cause: the GitHub Actions job steps that set up Ollama and pulled the two GGUF models (per .github/workflows/prompt-optimization.lock.yml, lines ~503-528) run in the outer GitHub-hosted runner, but this agent executes inside the stricter docker-sudo-iptables sandbox, whose egress allowlist (defaults, node, local) does not include hf.co/huggingface.co, and the host's already-running Ollama server (if started) was not port-forwarded into this container despite allow-host-ports: [11434].
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/38310132548
Manually invoke the agent
Debug this workflow failure using your favorite Agent CLI and the agentic-workflows prompt.
- Start your agent
- Load the
agentic-workflowsskill from.github/skills/agentic-workflows/SKILL.mdor https://github.com/github/gh-aw/blob/main/.github/skills/agentic-workflows/SKILL.md - Type
debug the agentic workflow prompt-optimization failure in https://github.com/githubnext/gh-aw-wizard/actions/runs/38310132548
[!TIP]
Stop reporting this workflow as a failure
To stop a workflow from creating failure issues, set
report-failure-as-issue: falsein its frontmatter:safe-outputs: report-failure-as-issue: false
Generated from Prompt Optimization · copilot · 100.3 AIC · ◷
- 主要语言
- JavaScript
- 星标
- 6
- 派生
- 1
- 平均合并
- 1 天 5 小时
- 30 天内合并 PR
- 21
环境准备
这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
githubnext/gh-aw-wizard 的其他 Issue
-
deep-research
难度 1/5 1 小时以内 新手友好度 65/100
githubnext/gh-aw-wizard#314 ·
维护者通常 1 天内回复
-
agentic-workflows
难度 1/5 1 小时以内 新手友好度 25/100
githubnext/gh-aw-wizard#340 ·
维护者通常 1 天内回复
-
agentic-workflows
难度 4/5 3-5 天 新手友好度 35/100
githubnext/gh-aw-wizard#338 ·
维护者通常 1 天内回复
-
难度 3/5 1-2 天 新手友好度 25/100
githubnext/gh-aw-wizard#336 ·
维护者通常 1 天内回复
-
agentic-workflows
难度 4/5 1-2 天 新手友好度 12/100
githubnext/gh-aw-wizard#334 ·
维护者通常 1 天内回复
查看 githubnext/gh-aw-wizard 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 76/100
bigcapitalhq/bigcapital#1544 · 1 条评论 ·
维护者通常 1 天内回复
-
help wanted kind/bug
难度 2/5 1-3 小时 新手友好度 78/100
meshery/meshery.io#3112 ·
维护者通常 2 天内回复
-
area:docs type:chore
难度 2/5 1-3 小时 新手友好度 82/100
bulkhead-labs/tailsuite#31 ·
-
dependencies javascript
难度 2/5 1-3 小时 新手友好度 70/100
gems-uff/noworkflow#470 ·
维护者通常 3 天内回复
-
product / auth product / console product / sites product / storage
难度 1/5 1 小时以内 新手友好度 84/100
维护者通常 1 天内回复