Config key duplication and Telegram message delivery fixes
NousResearch/hermes-agent · cluster 71047 · hermes cli
Data as of
Nothing open on GitHub. Fix merged in #75867. Check it covers your case.
The short answer
- Known?
- Yes. 7 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #75867. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #100893. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These items address bugs where config set could create duplicate or conflicting keys, and where Telegram streaming with reply_to_mode='first' delivered duplicate final messages. Fixes include guards against overwriting dict sections with scalars and redirecting certain platform display settings to the correct config path.
Open issues0
Open PRs0
Fixes on record
-
#75867 fix(config): guard against scalar overwrite of mapping sections (#74995)
files:
hermes_cli/config.py,tests/hermes_cli/test_set_config_value.py -
#100601 fix(telegram): stop duplicate final bubble after flood-capped finalize with reply_to_mode=first (#71047)
files:
gateway/stream_consumer.py,tests/gateway/test_telegram_final_delivery.py -
#100893 hermes config set platforms.<name>.<display_setting> now writes the display.platforms key the gateway reads (#71047, salvage #78111)
files:
contributors/emails/[redacted:email],hermes_cli/config.py,tests/hermes_cli/test_config_set_platforms_redirect.py,website/docs/user-guide/configuration.md
3 PRs closed without merging
From the close comments: done elsewhere 2 · merged via another change 1
-
#71076 fix(config+telegram): prevent duplicate config key and duplicate message delivery (#71047) · done elsewhere →
fab3643,#100601,#100893 -
#71387 fix(cli): guard config set against overwriting dict sections with scalars · done elsewhere →
#75867,#75409 -
#78111 fix(config): redirect platforms.<name>.<display_setting> to display.platforms.<name>.<setting> (#71047) · merged via another change →
c345d81,#100893
Closed issues · 1
- Closed#71047Bug: config set duplicates top-level key + Telegram streaming+reply_to_mode='first' duplicates final message
How this cluster was grouped
-
Link evidence (
structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference. -
Pairwise link density
0.29: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36.1.00means every pair is linked.
Pick up a Lab task
Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.
Open the Lab