Fix misleading storage size reporting in optimize-storage
Cluster 70146. Data as of
Nothing open on GitHub. Fix merged in #71200 on 25 Jul 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 #71200. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #71200. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These items address a bug where the optimize-storage command incorrectly reports negative or misleading 'reclaimed' space when the database size increases instead of decreasing. Fixes adjust the output to accurately reflect size changes in both directions.
Open issues0
Open PRs0
Fixes on record
-
#71200 fix(sessions): report truthful reclaimed space after optimize (#70146)
files:
contributors/emails/[redacted:email],hermes_cli/main.py,hermes_state.py,tests/hermes_cli/test_sessions_size_delta_label.py,tests/test_hermes_state.py
1 PR closed without merging
From the close comments: merged via another change 1
-
#70175 fix(cli): show 'grew by' when optimize-storage DB size increases (#70146) · merged via another change →
58b2a8c,#71200
Closed issues · 1
- Closed#70146hermes sessions optimize-storage reports negative "reclaimed" size
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
- #71200
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 25 Jul 2026