Terminal fence markers leaking into file read content
Cluster 5400 · environments. Data as of
Nothing open on GitHub. Fix merged in #19426 on 3 May 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 #19426. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #19426. That is separate from the fix event. - Still open
- Nothing open on GitHub.
The members concern HERMES_FENCE terminal fence markers appearing in file content via ShellFileOperations, reportedly corrupting source files. Two members are pull requests (or similarly titled items) proposing to strip these leaked fences from reads, and one is a bug report describing the problem.
Open issues0
Open PRs0
Fixes on record
-
#19426 fix(file): strip leaked terminal fences from reads
files:
tests/tools/test_file_operations.py,tools/file_operations.py
1 PR closed without merging
From the close comments: merged via another change 1
-
#19266 fix(file): strip leaked terminal fences from reads · merged via another change →
#19426
Closed issues · 1
- Closed#5400[Bug]: HERMES_FENCE markers leak into file content via ShellFileOperations — corrupts source files silently
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
- Subsystem
- environments
- Merged PRs
- #19426
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 3 May 2026