Nothing open on GitHub. Fix merged in #14111. 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 #14111. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
unresolved. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These issues and PRs concern a bug where full-log uploads in a debug/share command drop lines that fall exactly on byte-boundary truncation points. The work involves identifying the problem and implementing boundary-safe truncation logic.
Open issues0
Open PRs0
Fixes on record
-
#14111 fix(debug): snapshot logs once, boundary-safe truncation, and sweep on all paths
files:
gateway/run.py,hermes_cli/debug.py,scripts/release.py,tests/gateway/test_debug_command.py,tests/hermes_cli/test_debug.py
3 PRs closed without merging
From the close comments: duplicate 2 · done elsewhere 1
-
#13994 feat(cli): add hermes debug share with byte-boundary-safe log truncation · done elsewhere →
#8681,#10510,#11240,#11843,#14040,#14111 -
#14039 fix(debug): preserve exact-boundary tail lines in full-log uploads · duplicate →
#14040,#13968 -
#14040 fix: preserve full-log lines at truncation boundaries · duplicate →
#14039,#13968
Closed issues · 1
- Closed#13968debug share full-log truncation drops a whole line at exact byte boundaries
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
- Merged PRs
- #14111
- Closed issues
- 1
- Attempts
- 3 PRs closed without merging
- Fix link checked
- 22 Apr 2026. This confirmation is old and may be out of date (a revert or reopen would not have invalidated it here); re-verify.