[aw] Rig Skill Integration - DeepSeek Harness: engine driver crashed
Mantenedores costumam responder em até 1 dia
Ninguém assumiu esta issue ainda.
Avaliação
- Dificuldade
- 4/5
- Tempo estimado
- 3-5 dias
- Facilidade para iniciantes
- 35/100
- Tipo de issue
- Bug
- Clareza
- Razoavelmente clara
- Status de atividade
- Ativa
- Stack de tecnologia
- github-actions, typescript
Direção de pesquisa
Start with the failed run linked from the issue and the workflow source at .github/workflows/rig-skill-integration-deepseek.md. The available evidence says the DeepSeek Harness driver exited with code 1 before producing terminal safe output, but gives no stderr diagnostic or failing tool call. Trace the run through that workflow to identify the crash; done means the harness completes and records terminal safe output.
Escrita pelo modelo de indexação a partir do texto da issue.
Descrição
What happened
Rig Skill Integration - DeepSeek Harness engine driver crashed.
View run #40206144829 · 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.
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/40206144829
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 1, 2026, 3:19 PM UTC
- Linguagem predominante
- TypeScript
- Estrelas
- 14
- Forks
- 0
- Merge médio
- 9h 27min
- PRs com merge (30d)
- 34
Preparar o ambiente
Este projeto não oferece contêiner de desenvolvimento, Dockerfile nem guia de contribuição, então a configuração fica por sua conta: comece pelo README e veja nosso guia da primeira contribuição para os passos gerais.
Primeiros passos
- Leia a issue inteira e depois o guia de contribuição do projeto.
- Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
- Faça um fork do repositório e trabalhe em uma branch.
- Abra um pull request que referencie o número da issue.
Mais de githubnext/rig
-
agentic-workflows
Dificuldade 5/5 Mais de uma semana Facilidade para iniciantes 25/100
githubnext/rig#724 ·
Mantenedores costumam responder em até 1 dia
-
ai-agent automation
Dificuldade 1/5 Menos de uma hora Facilidade para iniciantes 1/100
githubnext/rig#723 ·
Mantenedores costumam responder em até 1 dia
-
ai-agent automation
Dificuldade 1/5 Menos de uma hora Facilidade para iniciantes 10/100
githubnext/rig#721 ·
Mantenedores costumam responder em até 1 dia
-
agentic-workflows
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 38/100
githubnext/rig#720 ·
Mantenedores costumam responder em até 1 dia
-
agentic-workflows
Dificuldade 4/5 3-5 dias Facilidade para iniciantes 35/100
githubnext/rig#719 ·
Mantenedores costumam responder em até 1 dia
Todas as issues de githubnext/rig
Issues semelhantes
-
bug
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 76/100
awslabs/visual-asset-management-system#804 ·
Mantenedores costumam responder em até 1 dia
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 70/100
restatedev/sdk-typescript#813 ·
-
bug desktop P1 session XS
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 82/100
Mantenedores costumam responder em até 1 dia
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 62/100
Merit-Systems/x402scan#1312 ·
-
type:bug
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 78/100
Azure/apiops-cli#331 ·
Mantenedores costumam responder em até 3 dias