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 摘要。