Dmytro Danilenkov 58be7923cf git: Fix broken pipe error when blaming large untracked files (#67110)
## Summary

Split out of #66953.

Zed runs `git blame --contents -` and writes the buffer text into git's
stdin. when the file is not in HEAD (new or untracked), git exits
without reading stdin. if the buffer is over 64KB (checked on my macOS)
the write fails with `Broken pipe` and Zed returns that error instead of
empty blame. I guess on Linux it will also fail because 64 KB is default
pipe size.

steps to reproduce:
1. In git repository create an untracked file larger than 64 KB and open
it in Zed.
2. cmd+shift+p(macOS) and select "Run editor: toggle git blame"
3. On main you should get an error toast containing `Broken pipe`

<img width="1509" height="793" alt="Screenshot 2026-11-17 at 23 20 02"
src="https://github.com/user-attachments/assets/663550fc-44d7-4a57-add4-c45415a73bb9"
/>

the fix: check git exit status first and report the write error only
after that.

after fix no error:
<img width="1509" height="807" alt="Screenshot 2026-11-17 at 23 29 18"
src="https://github.com/user-attachments/assets/f570f228-17c9-4149-93c9-5569cbfc751a"
/>



## Testing
manually tested, no broken pipe error.
Added `test_blame_untracked_path_with_large_contents`. On `main` it
fails with `Broken pipe (os error 32)`; with this change it passes. Ran
the `git` crate tests on macOS.

## Self-review

- [x] I've reviewed my diff for quality, security, reliability, and
performance.
- [x] N/A UI changes follow the
[checklist](https://zed.dev/docs/development/ui-checklist).
- [x] Tests cover the new or changed behavior.

Release Notes:

- Fixed git blame failing with a broken pipe error for large untracked
files.

Co-authored-by: Claude Fable 5.2 <noreply@anthropic.com>
2026-11-18 00:29:57 +00:00
…
2026-11-17 12:43:21 +00:00
…
2026-11-17 12:43:21 +00:00
2026-11-17 12:43:21 +00:00
2026-09-11 09:13:44 +00:00
…
…
…

Zed

Zed CI

Welcome to Zed, a high-performance, multiplayer code editor from the creators of Atom and Tree-sitter.


Installation

On macOS, Linux, and Windows you can download Zed directly or install Zed via your local package manager (macOS/Linux/Windows).

Other platforms are not yet available:

Developing Zed

Contributing

See CONTRIBUTING.md for ways you can contribute to Zed.

Also... we're hiring! Check out our jobs page for open roles.

Licensing

Zed source code is licensed primarily under GPL-3.0-or-later, with Apache-2.0 components where marked.

License information for third party dependencies must be correctly provided for CI to pass.

We use cargo-about to automatically comply with open source licenses. If CI is failing, check the following:

  • Is it showing a no license specified error for a crate you've created? If so, add publish = false under [package] in your crate's Cargo.toml.
  • Is the error failed to satisfy license requirements for a dependency? If so, first determine what license the project has and whether this system is sufficient to comply with this license's requirements. If you're unsure, ask a lawyer. Once you've verified that this system is acceptable add the license's SPDX identifier to the accepted array in script/licenses/zed-licenses.toml.
  • Is cargo-about unable to find the license for a dependency? If so, add a clarification field at the end of script/licenses/zed-licenses.toml, as specified in the cargo-about book.

Sponsorship

Zed is developed by Zed Industries, Inc., a for-profit company.

If you’d like to financially support the project, you can do so via GitHub Sponsors. Sponsorships go directly to Zed Industries and are used as general company revenue. There are no perks or entitlements associated with sponsorship.

S
Description
No description provided
Readme 1.6 GiB
Languages
Rust 95.4%
JSON-with-Comments 2.4%
Python 0.8%
Inno Setup 0.3%
Tree-sitter Query 0.3%
Other 0.4%