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

Offen
  • Stimmt etwas nicht?
#792 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Anfängerfreundlichkeit
38/100
Issue-Typ
Bug
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
github, github-actions, typescript
Bereich
ci-cd, devtools

Rechercherichtung

Start with the linked run and the workflow source at .github/workflows/rig-skill-integration-deepseek.md; follow the debugging instructions linked in the issue. Identify why the DeepSeek Harness driver exits with code 1 before emitting terminal safe output, then confirm the workflow completes successfully on a rerun.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

agentic-workflows
What happened

Rig Skill Integration - DeepSeek Harness engine driver crashed.

View run #41855547626 · 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/41855547626

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 11, 2026, 3:17 PM UTC
Vorherrschende Sprache
TypeScript
Sterne
14
Forks
0
Ø Merge
9 Std. 15 Min.
Gemergte PRs (30 T.)
35

Entwicklungsumgebung

Dieses Projekt bietet weder Dev-Container noch Dockerfile noch Beitragsleitfaden – die Einrichtung liegt bei Ihnen. Beginnen Sie mit der README; die allgemeinen Schritte stehen in unserem Leitfaden für den ersten Beitrag.

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus githubnext/rig

Alle Issues in githubnext/rig

Ähnliche Issues

Weitere Issues zu TypeScript

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.