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 reported incomplete result

Ouverte
  • Quelque chose ne va pas ?
#604 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
12/100
Type d'issue
Bug
Clarté
À clarifier
Activité
Active
Stack technique
typescript
Domaine
ai, authentication

Piste de recherche

The failure comes from running the rig program through skills/rig/rig.ts in both URI and --server modes, which both end in AUTHENTICATION_FAILED. Start with the run log linked in the issue and the rig program that uses input: s.object({ path: s.path }), then check how scripts/haiku.integration.test.ts authenticates. It is not clear what a fix looks like, so confirm the scope with a maintainer before writing code.

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/37945576194

[!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: 
Could not execute the requested rig program (project-summarizer) because no authenticated Copilot runtime is available for a nested session. The only reachable server (127.0.0.1:3002, from COPILOT_SDK_URI) is the harness's own engine instance and requires a connectionToken to accept a new session, which is not exposed to this sandbox. No COPILOT_GITHUB_TOKEN or other credential is available to spawn an independent authenticated runtime via --server either.
Steps taken:
1. Fixed a schema bug in the supplied rig program (`input: { path: s.path }` must be `input: s.object({ path: s.path })` per rig's agent() API) and placed the file inside the repo tree so the `rig` module-alias import resolves (node_modules/rig symlink only resolves for files under the repo root).
2. Ran `echo '{}' | node skills/rig/rig.ts <program>` (URI transport, matching COPILOT_SDK_URI) — failed with AUTHENTICATION_FAILED.
3. Ran the same with `--server` (stdio transport, spawns a fresh bundled runtime) — also failed with AUTHENTICATION_FAILED, because no GitHub token / API key is available to that fresh process (COPILOT_GITHUB_TOKEN, ANTHROPIC_API_KEY, etc. are not present in env; COPILOT_API_KEY/COPILOT_TOKEN are dummy/offline-mode values scoped to the harness's own session, not to independently spawned copilot-sdk client processes).
4. Confirmed via the harness log (/tmp/gh-aw/sandbox/agent/logs/process-*.log) that port 3002 is the harness's own CLI server instance, and that connecting to it as a second client requires a connectionToken (env var COPILOT_CONNECTION_TOKEN) that is unset and not discoverable without probing restricted internals, which I avoided per policy.

No issue was created, since the actual project summary could not be produced. A human would need to either provide a COPILOT_GITHUB_TOKEN/connection token, or run this from an environment where `rig` can establish its own authenticated Copilot session (e.g., locally with `gh auth login` / a personal token, as done in scripts/haiku.integration.test.ts).

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/37945576194
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 · 117.1 AIC · ◷

  • expires on Oct 16, 2026, 2:48 PM UTC
Langage dominant
TypeScript
Étoiles
14
Forks
0
Merge moyen
3 h 38 min
PR mergées (30 j)
29

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.