Issue Station
Sign In
Tools hereToolbox

hermes - ✅(Solved) Fix [Bug]: kanban boads rm --delete does not delete boards [1 pull requests, 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#23139•Fetched 2026-05-11 03:30:51
View on GitHub
Comments
0
Participants
1
Timeline
5
Reactions
0
Author
jonmachjonmach
Participants
jonmachjonmach
Timeline (top)
labeled ×3cross-referenced ×2

Error Message

Additional Logs / Traceback (optional)

Root Cause

Root Cause Analysis (optional)

Fix Action

Fixed

PR fix notes

PR #23302: fix: 4 small surgical bugs — kanban delete alias, gateway title noise, bg truncation, cprint coroutine

Description (problem / solution / changelog)

Four independent one-area fixes, each with its own root cause analysis.

Fix 1 — kanban boards delete alias archives instead of deletes (#23139)

The delete subcommand alias shares _cmd_boards_rm but the --delete flag belongs only to the rm subparser. getattr(args, 'delete', False) therefore returns False when the alias is used, so remove_board(archive=True) runs — archiving the board instead of deleting it.

Fix: detect boards_action == 'delete' and treat it as force_delete=True. Test added.

Fix 2 — Gateway auto-title failure leaks as user-visible message (#23246)

When background title generation fails (e.g. HTTP 401 on auxiliary provider), _emit_auxiliary_failure routes the error through _emit_warning, which delivers it as a visible ⚠ message in Slack/Telegram/WhatsApp. Not actionable to the end user.

Fix: replace the failure_callback in Gateway mode with a debug-log-only lambda.

Fix 3 — Background process notification starts mid-line when output is truncated (#23284)

session.output_buffer[-2000:] truncates at an arbitrary byte offset, potentially starting the notification mid-line.

Fix: snap to the next newline boundary after the cut and prepend [… output truncated — showing last N chars] when content was dropped.

Fix 4 — _cprint() silently drops output from background threads (#23185 Bug A)

run_in_terminal() returns a coroutine (Future). Passing it bare to call_soon_threadsafe schedules the callback but never awaits the coroutine — Python garbage-collects it with RuntimeWarning, silently dropping the output.

Fix: wrap with asyncio.ensure_future() so the coroutine is properly scheduled on the running loop.

Changed files

  • cli.py (modified, +18/-5)
  • gateway/run.py (modified, +23/-8)
  • hermes_cli/kanban.py (modified, +6/-1)
  • scripts/release.py (modified, +1/-0)
  • tests/hermes_cli/test_kanban_boards.py (modified, +33/-0)
  • tools/process_registry.py (modified, +1/-1)

Code Example

hermes kanban boards rm phase3-retest --delete
Board 'phase3-retest' deleted.

---

$ hermes kanban boards ls | grep -i phase3
    phase3-retest             Phase3 Retest                 (empty)

---

Debug report uploaded:
  Report       https://paste.rs/BnUbW
  agent.log    https://dpaste.com/6Q99D9JQA
  gateway.log  https://dpaste.com/9VL5TT39S

---
RAW_BUFFERClick to expand / collapse

Bug Description

I tried to delete an existing kanban board using

hermes kanban boards rm phase3-retest --delete
Board 'phase3-retest' deleted.

Yet, it is still there:

$ hermes kanban boards ls | grep -i phase3
    phase3-retest             Phase3 Retest                 (empty)

Steps to Reproduce

As above:

  1. List the existing kanban boards using hermes kanban boards ls
  2. Pick a board to delete using hermes kanban boards rm <your board slug> --delete
  3. List the existing kanban boards and it will still be there.

Expected Behavior

The board should no longer be in the list

Actual Behavior

See above: The board remains in the list No errors appeared

Affected Component

Tools (terminal, file ops, web, code execution, etc.)

Messaging Platform (if gateway-related)

N/A (CLI only)

Debug Report

Debug report uploaded:
  Report       https://paste.rs/BnUbW
  agent.log    https://dpaste.com/6Q99D9JQA
  gateway.log  https://dpaste.com/9VL5TT39S

Operating System

Debian GNU/Linux 12 (bookworm) (with node:20 container)

Python Version

3.11.2

Hermes Version

No response

Additional Logs / Traceback (optional)

Root Cause Analysis (optional)

No response

Proposed Fix (optional)

No response

Are you willing to submit a PR for this?

  • I'd like to fix this myself and submit a PR

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…
#file not found#serialization error#model compatibility#GPU setup#container setup

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 - ✅(Solved) Fix [Bug]: kanban boads rm --delete does not delete boards [1 pull requests, 1 participants]