Issue Station
Sign In
Tools hereToolbox

hermes - 💡(How to fix) Fix Reduce recurring Hermes pending-task gateway/log noise [3 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
NousResearch/hermes-agent#19823•Fetched 2026-05-05 06:04:54
View on GitHub
Comments
3
Participants
2
Timeline
8
Reactions
0
Author
emm3ttarmstrongemm3ttarmstrong
Participants
alt-glitchalt-glitchemm3ttarmstrongemm3ttarmstrong
Timeline (top)
commented ×3labeled ×3closed ×1cross-referenced ×1

Recurring error/warning appeared 14 times recently: Task was destroyed but it is pending!

Error Message

Recurring error/warning appeared 14 times recently: Task was destroyed but it is pending!

Root Cause

Recurring error/warning appeared 14 times recently: Task was destroyed but it is pending!

RAW_BUFFERClick to expand / collapse

Why

Hermes is repeatedly logging Task was destroyed but it is pending!. Emmett has approved this recurring Signal Deck card multiple times, so it should be durable repo-native reliability work rather than cycling through the decision inbox.

Signal Deck card

  • Card ID: ops-ops-task-was-destroyed-but-it-is-pending
  • Work item ID: ops-ops-task-was-destroyed-but-it-is-pending:approve:2026-05-04T16:24:04.476Z:work
  • Decision/action: approve at 2026-05-04T16:24:04.476Z
  • Project: Hermes / Ops Reliability
  • Source: Signal Deck action processor run 60fd4c81-0c29-434d-bff3-e54b65393c9b

User feedback / approval

I’ve approved this like 5 times

Context

Recurring error/warning appeared 14 times recently: Task was destroyed but it is pending!

Scope

Investigate the gateway/runtime path that leaves asyncio tasks pending at shutdown or stream cancellation, identify the source, and either implement a safe fix or document why the warning is expected/noisy.

Original Signal Deck prompt:

Approve a bounded investigation/fix only if this improves Hermes reliability or reduces future agent friction.

Acceptance criteria

  • Identify the component/call path producing Task was destroyed but it is pending!.
  • Determine whether it is a real cleanup bug, expected cancellation noise, or a third-party/runtime artifact.
  • Implement a safe local fix or logging/cancellation guard if actionable.
  • Add or update a regression test where practical, or document a concrete manual verification path.
  • Link implementation PR back to this issue and preserve the Signal Deck card ID in the PR body.

Evidence

  • No explicit file evidence attached in the card; card context is the provenance.
  • Similar recurring Hermes gateway/log-noise issue already exists for another warning: #18485.

Out of scope / risk gates

  • Do not deploy, publish publicly, spend money, touch credentials/tokens/secrets, contact clients, or send Slack/Telegram/Discord messages from this issue alone.
  • Keep implementation work on a branch and PR linked to this issue.

extent analysis

TL;DR

Investigate the gateway/runtime path in Hermes that leaves asyncio tasks pending at shutdown or stream cancellation to identify the source of the Task was destroyed but it is pending! error.

Guidance

  • Review the asyncio task management in Hermes to ensure proper cleanup and cancellation of tasks during shutdown or stream cancellation.
  • Investigate the component/call path producing the error to determine if it's a real cleanup bug, expected cancellation noise, or a third-party/runtime artifact.
  • Consider implementing a safe local fix or logging/cancellation guard if the issue is deemed actionable.
  • Add or update a regression test to verify the fix, if practical, or document a concrete manual verification path.

Example

No specific code snippet can be provided without more context, but reviewing the asyncio task management and cancellation logic in Hermes is a good starting point.

Notes

The issue may be related to the way Hermes handles asyncio tasks during shutdown or stream cancellation. Further investigation is needed to determine the root cause and implement a safe fix.

Recommendation

Apply workaround: Implement a safe local fix or logging/cancellation guard to mitigate the Task was destroyed but it is pending! error, as it is likely related to the asyncio task management in Hermes.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#ISR setup#authentication setup#request error#file not found#serialization error

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

hermes - 💡(How to fix) Fix Reduce recurring Hermes pending-task gateway/log noise [3 comments, 2 participants]