Reduce excess Git Bash process spawns in read_file
Cluster 90039 · agent. Data as of
Nothing open on GitHub. Fix merged in #101599 on 2 Sep 2026. Check it covers your case.
The short answer
- Known?
- Yes. 4 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #101599. 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 items identify that read_file triggers an unusually high number of Git Bash process starts on Windows per read operation. The associated fixes aim to coalesce those backend probes into fewer executions.
Open issues0
Open PRs0
Fixes on record
-
#101599 perf(file-ops): collapse read_file/write_file shell probes into one round-trip (salvage #95160)
files:
contributors/emails/[redacted:email],tests/tools/file_ops_fakes.py,tests/tools/test_file_operations.py,tests/tools/test_file_operations_edge_cases.py,tests/tools/test_file_ops_single_roundtrip.py,tools/file_operations.py
2 PRs closed without merging
From the close comments: duplicate 1 · superseded by another PR 1
Closed issues · 1
- Closed#90039read_file pays 4–5 Git Bash process starts per text read on Windows
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.50: 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
- agent
- Merged PRs
- #101599
- Closed issues
- 1
- Attempts
- 2 PRs closed without merging
- Fix link checked
- 2 Sep 2026