[aw] Failed jobs: Daily Caveman Optimizer

Abierto
  • ¿Algo no está bien?
#77,226 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
45/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
github-actions, go
Área
ci-cd

Línea de trabajo

Start with the linked workflow, .github/workflows/daily-caveman-optimizer.md, and inspect the failed push_ledger_changes job, especially step 6, to trace why the gh-aw-ledger-transactions artifact was unavailable. Follow the artifact upload and download steps to locate the mismatch. Done when the workflow reliably makes the ledger transaction artifact available to the publishing job and the job completes.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

agentic-workflows
Failed Jobs in Workflow Run

Workflow: Daily Caveman Optimizer
Run: https://github.com/github/gh-aw/actions/runs/43302931680

The following jobs failed in this workflow run:

  • push_ledger_changes

    Failed step numbers (up to 10): 6. See the linked job for details.

    2026-11-12T20:45:35.4184887Z ##[error]Unable to download artifact(s): Artifact not found for name: gh-aw-ledger-transactions
2026-11-12T20:46:04.7536198Z Error: Failed to read validated ledger transaction artifact
2026-11-12T20:46:04.7541196Z   [cause]: Error: ENOENT: no such file or directory, open '/home/runner/work/_temp/gh-aw/ledger-transactions.json'
2026-11-12T20:46:04.7607230Z ##[error]Unhandled error: Error: Failed to read validated ledger transaction artifact

Failure boundary: Non-agent job. A downstream publishing failure is separate from an engine driver process failure and does not establish a provider outage.

A failure boundary identifies where failure was observed, not its cause: either the engine driver process or a non-agent job. The job result and failed step numbers locate the failure, but do not identify its cause. Inspect the linked job before attributing it to validation, permissions, infrastructure, or an external service. If no failed step metadata is available, use the linked workflow run.

Step diagnostics contain only bounded runtime metadata; step names, agent text, prompts, and tool payloads are excluded.

  • expires on Nov 19, 2026, 8:46 PM UTC
Lenguaje dominante
Go
Estrellas
5.6k
Forks
625
Merge medio
5 h 39 min
PR fusionados (30 d)
796

Preparar el entorno

Abrir en Codespaces

Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de github/gh-aw

Todos los issues de github/gh-aw

Issues similares

Más issues de Go

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.