YAML config scalar mutation and data loss fixes
NousResearch/hermes-agent · cluster 119844 · other
Data as of
Nothing open on GitHub. Fix merged in #120343. Check it covers your case.
The short answer
- Known?
- Yes. 5 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #120343. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #120343. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These issues and pull requests address bugs in config.yaml handling where ruamel-yaml re-folding silently mutated long quoted scalars, and where transient read errors could wipe config contents. The work focuses on preserving stored values accurately during config read and write operations.
Open issues0
Open PRs0
Fixes on record
-
#120343 fix(config): a transient read error no longer wipes config.yaml (explicit nulls kept, no phantom agent section; salvage #105828, #119846)
files:
gateway/slash_commands.py,hermes_cli/auth.py,hermes_cli/config.py,hermes_cli/config_effective.py,hermes_cli/config_read_errors.py,hermes_cli/web_routers/config_env.py,hermes_cli/xai_retirement.py,tests/hermes_cli/test_config.py,tests/hermes_cli/test_config_save_integrity.py,tests/hermes_cli/test_resolve_provider_corrupt_config.py,tests/hermes_cli/test_xai_retirement.py,tests/test_utils_atomic_roundtrip_yaml_save.py,tui_gateway/server.py,utils.py
3 PRs closed without merging
From the close comments: done elsewhere 1 · merged via another change 1 · other 1
-
#119846 fix(config): preserve long quoted scalars · done elsewhere →
7f59505,2f0cab5,b0369c4,8afaab3,#120343 -
#120278 fix(config): stop YAML re-folding from mutating stored config scalars (#119844) · merged via another change →
7f59505,2f0cab5,b0369c4,8afaab3,#119846,#120343 -
#127439 fix: fix/119844-ruamel-yaml-fold · other →
#119844
Closed issues · 1
- Closed#119844[Bug]: config saves silently insert spaces into long double-quoted scalars (ruamel re-folding mutates stored values)
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.40: 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 LabAt a glance
- Subsystem
- other
- Merged PRs
- #120343
- Closed issues
- 1
- Attempts
- 3 PRs closed without merging
- Fix link checked
- 23 Sep 2026