Hacktoberfest 2026 : les issues que les mainteneurs ont marquées pour octobre, ouvertes et accessibles aux débutants. Parcourir les issues Hacktoberfest

[aw] Daily Rig File Summarizer exhausted its prompt

Ouverte
  • Quelque chose ne va pas ?
#614 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

Personne n'a encore pris cette issue.

Évaluation

Difficulté
4/5
Temps estimé
3-5 jours
Accessibilité débutants
18/100
Type d'issue
Bug
Clarté
À clarifier
Activité
Active
Stack technique
github-actions, typescript
Domaine
devops

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

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
Langage dominant
TypeScript
Étoiles
13
Forks
0
Merge moyen
3 h 44 min
PR mergées (30 j)
28

Préparer son environnement

Ce projet ne fournit ni conteneur de développement, ni Dockerfile, ni guide de contribution : l'installation est à votre charge. Commencez par son README, et consultez notre guide de la première contribution pour les étapes générales.

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de githubnext/rig

Toutes les issues de githubnext/rig

Issues similaires

Plus d'issues TypeScript

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.