SocketDev / SocketDev/socket-btm

[aw] 🔁 Weekly Update failed

Open
#148 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

agentic-workflows
Dominant language
TypeScript
Stars
3
Forks
1
PR merge metrics
No merged PRs in 30d

Description

Workflow Failure

Workflow: 🔁 Weekly Update
Branch: main
Run: https://github.com/SocketDev/socket-btm/actions/runs/31682131170

[!WARNING]
Engine Failure: The claude engine terminated unexpectedly.

Last agent output:

2026-08-13T08:33:26.373Z [DEBUG] MCP server "safeoutputs": HTTP connection dropped after 184s uptime
2026-08-13T08:33:26.373Z [DEBUG] MCP server "safeoutputs": Connection error: SSE stream disconnected: AbortError: The operation was aborted.
2026-08-13T08:33:26.373Z [DEBUG] MCP server "safeoutputs": Terminal connection error 1/3
2026-08-13T08:33:26.378Z [DEBUG] MCP server "janus-multi": UNKNOWN connection closed after 184s (cleanly)
2026-08-13T08:33:26.378Z [DEBUG] MCP server "janus-multi": Cleared connection cache for reconnection
2026-08-13T08:33:26.383Z [DEBUG] MCP server "chrome-devtools": UNKNOWN connection closed after 183s (cleanly)
2026-08-13T08:33:26.383Z [DEBUG] MCP server "chrome-devtools": Cleared connection cache for reconnection
2026-08-13T08:33:26.422Z [DEBUG] MCP server "chrome-devtools": MCP server process exited cleanly
2026-08-13T08:33:26.422Z [DEBUG] MCP server "janus-multi": MCP server process exited cleanly
2026-08-13T08:33:26.425Z [DEBUG] LSP server manager shut down successfully
Action Required

Assign this issue to an agent to debug and fix the issue.

Debug with any coding agent

Use this prompt with any coding agent (GitHub Copilot, Claude, Gemini, etc.):

Debug the agentic workflow failure using https://raw.githubusercontent.com/github/gh-aw/main/debug.md

The failed workflow run is at https://github.com/SocketDev/socket-btm/actions/runs/31682131170
Manually invoke the agent

Debug this workflow failure using your favorite Agent CLI and the agentic-workflows prompt.

[!TIP]

Stop reporting this workflow as a failure

To stop a workflow from creating failure issues, set report-failure-as-issue: false in its frontmatter:

safe-outputs:
  report-failure-as-issue: false

Generated from 🔁 Weekly Update ·

  • expires on Aug 20, 2026, 8:34 AM UTC

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with .github/workflows/weekly-update.md and the failed run linked in the issue, then read the agentic-workflows guidance in .github/skills/agentic-workflows/SKILL.md and debug.md. Determine why the claude engine and its MCP connections terminated, and confirm that the Weekly Update workflow completes successfully without creating a failure issue.

Written by the indexing model from the issue text.

Assessment

Tech stack
github-actions
Domain
ci-cd
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.