Hacktoberfest 2026：维护者为十月标记出来的 issue，仍然开放、适合新手。 浏览 Hacktoberfest issue

[aw] Daily Rig File Summarizer exhausted its prompt

未关闭
  • 哪里不对？
#614 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
18/100
Issue 类型
缺陷
描述清晰度
需要澄清
活跃度
活跃
技术栈
github-actions, typescript
领域
devops

调研方向

Start with the workflow file .github/workflows/daily-rig-file-summarizer.md and the driver config in .github/drivers/copilot-sdk-driver.ts, then read skills/rig/harness-tools.md to see how run_rig is meant to be registered. The reported cause is that run_rig is missing from the MCP config, so check whether the engine.driver entry is needed there. Done means the workflow no longer reports a missing run_rig tool and emits a terminal safe output; this needs maintainer input on the intended setup.

由索引模型根据 Issue 内容生成。

描述

agentic-workflows
Workflow Failure

Workflow: Daily Rig File Summarizer
Branch: main
Run: https://github.com/githubnext/rig/actions/runs/38059894701

[!WARNING]
Missing Tools Reported: The agent reported missing tools during execution.

Missing Tools:

  • run_rig (Rig launch tool): The `run_rig` harness tool (docs: skills/rig/harness-tools.md) is required to run Rig programs with the Copilot SDK driver, but it is not registered in this workflow's MCP config (only `github` and `safeoutputs` are exposed). Running `node skills/rig/run.t
    [Content truncated due to length]

Alternatives:

Tool Alternative
run_rig (Rig launch tool) Register the `run_rig` tool via `.github/drivers/copilot-sdk-driver.ts` (as described in skills/rig/harness-tools.md) in the workflow's engine.driver config so the trusted SDK driver can hand off the connection token, then re-run the workflow.

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

Error details: 
missing_terminal_safe_output
Agent finished without emitting a terminal safe output; task completion could not be confirmed.
bash: env | grep -i RIG_; which run_rig 2>&1; type run_rig 2>&1: {"content":"/bin/bash: line 1: type: run_rig: not found\n(shellId: 35 completed with exit code 1)"}
Driver exit code: 0
Failure classification: prompt_exhaustion
Retry attempts observed: 0

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/rig/actions/runs/38059894701
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 Daily Rig File Summarizer · copilot · 75.2 AIC · ◷

  • expires on Oct 17, 2026, 2:39 PM UTC
主要语言
TypeScript
星标
13
派生
0
平均合并
1 小时 40 分钟
30 天内合并 PR
26

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

githubnext/rig 的其他 Issue

查看 githubnext/rig 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。