[aw] Rig Skill Integration - DeepSeek Harness: engine driver crashed
維護者通常 1 天內回覆
還沒有人認領這個 Issue。
評估
- 難度
- 4/5
- 預估耗時
- 1-2 天
- 新手友好度
- 35/100
- Issue 類型
- 缺陷
- 描述清晰度
- 需要釐清
- 活躍度
- 活躍
- 技術堆疊
- github-actions, typescript
- 領域
- devtools, testing-qa
研究方向
Start with the failed run linked in the issue and the .github/workflows/rig-skill-integration-deepseek.md workflow; the failing step is Execute DeepSeek Harness. Follow the linked debugging guide and investigate why the driver exits before recording terminal safe output. Done means identifying and addressing the cause, then confirming the workflow completes successfully.
由索引模型根據 Issue 內容生成。
描述
What happened
Rig Skill Integration - DeepSeek Harness engine driver crashed.
View run #41078734033 · 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/41078734033
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 6, 2026, 3:17 PM UTC
- 主要語言
- TypeScript
- 星號
- 14
- 分支
- 0
- 平均合併
- 9 小時 27 分鐘
- 30 天內合併 PR
- 34
環境準備
這個專案沒有提供開發容器、Dockerfile 或貢獻指南，環境需要你自己搭建：先看它的 README，通用步驟見我們的新手貢獻指南。
從這裡開始
- 先讀完整個 Issue，再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫，在一個分支上完成修改。
- 送出 Pull Request，並在描述裡引用這個 Issue 編號。
githubnext/rig 的其他 Issue
-
ai-agent automation
難度 3/5 1-2 天 新手友好度 45/100
githubnext/rig#759 ·
維護者通常 1 天內回覆
-
ai-agent automation
難度 5/5 一週以上 新手友好度 15/100
githubnext/rig#757 ·
維護者通常 1 天內回覆
-
agentic-workflows
難度 3/5 1-2 天 新手友好度 52/100
githubnext/rig#756 ·
維護者通常 1 天內回覆
-
ai-agent automation
難度 5/5 一週以上 新手友好度 25/100
githubnext/rig#755 ·
維護者通常 1 天內回覆
-
agentic-workflows
難度 4/5 3-5 天 新手友好度 35/100
githubnext/rig#753 ·
維護者通常 1 天內回覆
相似的 Issue
-
難度 2/5 1-3 小時 新手友好度 72/100
mihaip/infinite-mac#475 ·
-
難度 2/5 1-3 小時 新手友好度 83/100
marmelab/atomic-crm#401 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 82/100
維護者通常 1 天內回覆
-
enhancement good first issue
難度 2/5 1-3 小時 新手友好度 75/100
Deltares/webgl-streamline-visualizer#83 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 88/100
維護者通常 1 天內回覆