Cairn

Boolean string parsing bugs and fixes

NousResearch/hermes-agent · cluster 26721 · agent

Data as of

6 open items. Fix attempted, not merged.

The short answer

2open issues
4open PRs
13items grouped
Known?
Yes. 13 related items grouped here, 2 issues already closed.
Fix event
No fix has been merged to main. 5 PRs closed without merging; see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
2 issues and 4 PRs.

Multiple bug reports and fixes addressing cases where quoted string values like "false" were not correctly interpreted as boolean false in config, voice, gateway, and dependency-install paths. One unrelated performance fix for pre-compiling regex patterns is also present.

Open issues2

  • Issue#36648Quoted false still permits lazy dependency installs
  • Issue#41902[Bug]: utils.py

Open PRs4

  • PR#37328fix(deps): honor quoted false lazy-install opt-out (#36648)
  • PR#41991fix(utils): preserve env_bool defaults for unset vars
  • PR#41992[verified] fix: honor env defaults for missing variables
  • PR#49884fix(voice): respect false-like beep_enabled strings

5 PRs closed without merging

From the close comments: superseded by another PR 2 · closed without comment 1 · duplicate 1 · other 1

  • #26741 fix(gateway): coerce quoted "false" string to bool for platform enabled (#26721) · superseded by another PR → #27261
  • #32713 fix(core): pre-compile regex patterns across 5 files for performance · superseded by another PR → 3289927
  • #50127 fix(config): use is_truthy_value() for config boolean parsing across 8 paths · closed without comment
  • #50257 fix: parse voice beep_enabled with truthy helper · duplicate → #49884, #49883
  • #54419 fix(config): use is_truthy_value() for config boolean parsing · other → 9be292f
Closed issues · 2
  • Closed#26721[Bug] platforms.<name>.enabled: "false" (quoted) doesn't disable platform
  • Closed#49883[Bug]: voice.beep_enabled treats quoted false-like config strings as enabled
How this cluster was grouped
  • Link evidence (partly structural links): some members are connected by structural evidence (shared changed files, or a closing/superseded reference); the rest are joined by an automated relevance judgement over their text.
  • Members outside that structural core may belong to a different underlying problem.
  • Pairwise link density 0.13: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36. 1.00 means 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

At a glance

Subsystem
agent
Closed issues
2
Attempts
5 PRs closed without merging

For your agent

The same facts, typed.

cluster/26721.json
cluster/26721.md