hermes - 💡(How to fix) Fix journal-watcher: false-positive incidents for normal Director exits [1 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#15322Fetched 2026-04-25 06:22:56
View on GitHub
Comments
0
Participants
1
Timeline
4
Reactions
0
Author
Participants
Timeline (top)
labeled ×3closed ×1

Fix Action

Fix

Commit: 842f6c3

Removed 4 noise matchers from scripts/journal-watcher.sh. Only genuine failure patterns remain:

  • secret_detected (high)
  • director_exit_nonzero (code 1-9, high)
  • director_spawn_fail / director_restart_fail (high)
  • developer_spawn_fail / developer_failed (high)
  • bridge_disconnected (normal)

Also archived 4 false-positive incidents to archive/incidents-resolved-2026-04.md.

Status: CLOSED — fixed in commit 842f6c3

RAW_BUFFERClick to expand / collapse

Problem

journal-watcher was creating INCIDENT_QUEUE entries for normal Director/Developer lifecycle events:

  • director_exit — fired on every Director exit, including code:0 (normal)
  • director_spawned — fired on every Director spawn (normal operation)
  • developer_spawned — fired on every Developer spawn (normal operation)
  • developer_exit_nonzero — fired on developer exits with code 1-9 (routine, not failures)

All 3 Director exits in events.jsonl have code:0 — completely normal operation.

Fix

Commit: 842f6c3

Removed 4 noise matchers from scripts/journal-watcher.sh. Only genuine failure patterns remain:

  • secret_detected (high)
  • director_exit_nonzero (code 1-9, high)
  • director_spawn_fail / director_restart_fail (high)
  • developer_spawn_fail / developer_failed (high)
  • bridge_disconnected (normal)

Also archived 4 false-positive incidents to archive/incidents-resolved-2026-04.md.

Status: CLOSED — fixed in commit 842f6c3

extent analysis

TL;DR

The issue can be resolved by removing unnecessary matchers from the journal-watcher.sh script to prevent false-positive INCIDENT_QUEUE entries.

Guidance

  • Review the journal-watcher.sh script to ensure only relevant failure patterns are matched, such as secret_detected, director_exit_nonzero, and director_spawn_fail.
  • Verify that the script is correctly ignoring normal lifecycle events like director_exit with code 0.
  • Check the events.jsonl file to confirm that only genuine failure events are being logged.
  • Consider archiving resolved incidents to prevent clutter and improve incident tracking.

Example

No code snippet is provided as the issue is resolved through a specific commit (842f6c3) and the changes are described in the issue body.

Notes

The provided solution is specific to the journal-watcher.sh script and may not apply to other similar issues. The commit 842f6c3 is mentioned as the fix, but its contents are not provided.

Recommendation

Apply the workaround by removing unnecessary matchers from the journal-watcher.sh script, as described in the issue body, to prevent false-positive INCIDENT_QUEUE entries. This approach is recommended as it directly addresses the root cause of the issue.

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…

Still need to ship something?

×6

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

Back to top recommendations

TRENDING