Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

[aw] Daily Rig File Summarizer reported incomplete result

Aperta
  • Qualcosa non va?
#604 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
12/100
Tipo di issue
Bug
Chiarezza
Da chiarire
Stato di attività
Attiva
Stack tecnologico
typescript
Ambito
ai, authentication

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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
Lingua principale
TypeScript
Stelle
13
Fork
0
Merge medio
3h 44m
PR unite (30g)
28

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di githubnext/rig

Tutte le issue di githubnext/rig

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.