[aw] Rig Skill Integration - DeepSeek Harness: engine driver crashed

未關閉
  • 哪裡不對？
#775 0 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

維護者通常 1 天內回覆

還沒有人認領這個 Issue。

評估

難度
4/5
預估耗時
1-2 天
新手友好度
25/100
Issue 類型
缺陷
描述清晰度
需要釐清
活躍度
活躍
技術堆疊
github-actions, typescript
領域
ci-cd

研究方向

Start with the failed run linked in the issue (run 41319844321) and the Execute DeepSeek Harness step log, since the report has no stderr. The workflow source is .github/workflows/rig-skill-integration-deepseek.md. Done means the driver exit cause is identified and either fixed or documented on the issue with the reproduction steps.

由索引模型根據 Issue 內容生成。

描述

agentic-workflows
What happened

Rig Skill Integration - DeepSeek Harness engine driver crashed.

View run #41319844321 · 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 a report_incomplete signal: 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/41319844321

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 8, 2026, 3:13 PM UTC
主要語言
TypeScript
星號
14
分支
0
平均合併
9 小時 15 分鐘
30 天內合併 PR
35

環境準備

這個專案沒有提供開發容器、Dockerfile 或貢獻指南，環境需要你自己搭建：先看它的 README，通用步驟見我們的新手貢獻指南。

從這裡開始

  1. 先讀完整個 Issue，再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫，在一個分支上完成修改。
  4. 送出 Pull Request，並在描述裡引用這個 Issue 編號。

githubnext/rig 的其他 Issue

查看 githubnext/rig 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。