fix duplicate log routing for multiple in-process profiles
Cluster 111268. Data as of
Nothing open on GitHub. Fix merged in #111448 on 15 Sep 2026. Check it covers your case.
The short answer
- Known?
- Yes. 3 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #111448. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #111448. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These items address a logging bug where multiple profiles or Hermes homes running in the same process incorrectly share or receive each other's log lines. The fixes aim to ensure each profile gets its own properly routed log output.
Open issues0
Open PRs0
Fixes on record
-
#111448 fix(logging): a second profile home in one process gets its own routed log, not every profile's lines (#111268, salvage #111269)
files:
hermes_logging.py,tests/test_hermes_logging.py
1 PR closed without merging
From the close comments: done elsewhere 1
-
#111269 fix(logging): a second Hermes home in one process gets a routed log, not an unfiltered handler · done elsewhere →
#111448
Closed issues · 1
- Closed#111268fix(logging): every profile an in-process dashboard/serve backend serves gets every other profile's log lines
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.67: 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
- Merged PRs
- #111448
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 15 Sep 2026