[aw] Rig Skill Integration - DeepSeek Harness: engine driver crashed
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 12/100
- Tipo de issue
- Error
- Claridad
- Necesita aclaración
- Estado de actividad
- Activo
- Stack tecnológico
- github-actions, typescript
- Área
- devtools
Línea de trabajo
The failure is recorded in the generated workflow .github/workflows/rig-skill-integration-deepseek.md, whose failing step is Execute DeepSeek Harness in run 41469564343. The payload gives no stack trace or stderr, so the first step is opening that run's logs to find the driver exit reason. Done means the driver exits with a terminal safe output recorded, or the failure is classified and reported with a specific cause.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
What happened
Rig Skill Integration - DeepSeek Harness engine driver crashed.
View run #41469564343 · Workflow source · Previous failures
Branch: main
Next step
Review the failure details below for a targeted fix, or assign this issue to a coding agent to investigate.
Failure details
Runtime evidence
[!WARNING]
Task Could Not Be Completed: The workflow recorded areport_incompletesignal: the task was not completed or completion could not be confirmed.
Error details:
Failure classification: driver_crash
Driver exit code: 1. The engine driver exited before a terminal safe output was recorded.
Driver exit meaning: General failure
Last driver stderr summary: not recorded (no classified stderr diagnostic)
Last tool call status: not recorded
Failed tool calls observed: 0
Token budget state: unknown (no exhaustion signal recorded)
Step budget state (LLM invocations): unknown (no exhaustion signal recorded)
Safe-output tools: available at gateway snapshot (registered 5 tools)
Safe-output CLI calls observed: unknown (not recorded)
Safe-output MCP calls observed: 0
Safe-output persistence: not recorded
Agent finished without emitting a terminal safe output; task completion could not be confirmed.
Last engine error type: unknown
Retry attempts observed: 0
A comment or other safe output does not confirm that the requested task was completed. Only inferred runtime status and error codes are reported; agent text is excluded.
Failure Diagnostics
Agent job: agent
Agent job conclusion: failure
Failing step: Execute DeepSeek Harness
No additional engine error was captured. Check the reported failure signals and linked run for details.
Only runtime metadata is shown; agent-generated text is excluded.
Copy a debugging prompt
Paste this into your coding agent:
Debug the agentic workflow "rig-skill-integration-deepseek" failure.
Follow https://raw.githubusercontent.com/github/gh-aw/main/debug.md
Failed run: https://github.com/githubnext/rig/actions/runs/41469564343
If the repository includes the agentic-workflows skill, load it before investigating.
Manage failure notifications
To stop creating failure issues for this workflow, set this in its frontmatter and recompile:
safe-outputs:
report-failure-as-issue: false
This only disables issue reporting; it does not fix the failure.
Generated from Rig Skill Integration - DeepSeek Harness · ◷
- expires on Nov 9, 2026, 3:19 PM UTC
- Lenguaje dominante
- TypeScript
- Estrellas
- 14
- Forks
- 0
- Merge medio
- 9 h 15 min
- PR fusionados (30 d)
- 35
Preparar el entorno
Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de githubnext/rig
-
[aw] Upgrade availableAbiertoagentic-workflows
Dificultad 1/5 Menos de una hora Aptitud para principiantes 20/100
githubnext/rig#785 ·
Los mantenedores suelen responder en 1 día
-
agentic-workflows
Dificultad 3/5 Medio día Aptitud para principiantes 22/100
githubnext/rig#784 ·
Los mantenedores suelen responder en 1 día
-
agentic-workflows
Dificultad 3/5 Medio día Aptitud para principiantes 22/100
githubnext/rig#783 ·
Los mantenedores suelen responder en 1 día
-
agentic-workflows
Dificultad 3/5 Medio día Aptitud para principiantes 22/100
githubnext/rig#781 ·
Los mantenedores suelen responder en 1 día
-
agentic-workflows
Dificultad 3/5 Medio día Aptitud para principiantes 25/100
githubnext/rig#780 ·
Los mantenedores suelen responder en 1 día
Todos los issues de githubnext/rig
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
Los mantenedores suelen responder en 1 día
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 82/100
unocss/unocss#5421 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
needs-area
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
Azure/typespec-azure#5936 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 Medio día Aptitud para principiantes 72/100
vercel-labs/scriptc#2910 ·
Los mantenedores suelen responder en 1 día
-
automation missing-model model-sync provider:fireworks-ai
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
anomalyco/models.dev#12458 ·
Los mantenedores suelen responder en 1 día