Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

[aw] Daily Rig File Summarizer exhausted its prompt

Offen
  • Stimmt etwas nicht?
#614 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Anfängerfreundlichkeit
18/100
Issue-Typ
Bug
Klarheit
Muss geklärt werden
Aktivitätsstatus
Aktiv
Tech-Stack
github-actions, typescript
Bereich
devops

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

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
Vorherrschende Sprache
TypeScript
Sterne
13
Forks
0
Ø Merge
1 Std. 40 Min.
Gemergte PRs (30 T.)
26

Entwicklungsumgebung

Dieses Projekt bietet weder Dev-Container noch Dockerfile noch Beitragsleitfaden – die Einrichtung liegt bei Ihnen. Beginnen Sie mit der README; die allgemeinen Schritte stehen in unserem Leitfaden für den ersten Beitrag.

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus githubnext/rig

Alle Issues in githubnext/rig

Ähnliche Issues

Weitere Issues zu TypeScript

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.