Remco Smits 7ea077c78b fs: Improved responsiveness when watching paths on slow or unresponsive filesystems (#63410)
# Objective

When Zed watches a file or folder that doesn't exist yet, it retries
every couple of seconds. Two steps in that retry can be slow: asking the
filesystem whether it's case-sensitive (blocking sys call), and
registering the watcher itself (which reads the whole folder tree when
the watcher is recursive). If the system is slow to respond, those steps
can hang for a long time as you can see inside the following logs:

```
2026-08-23T11:42:56+02:00 INFO  [zed::reliability::hang_detection::logging] Background hang detected on Unknown:
Tasks(s) that ran too long
18.159457333s        - crates/fs/src/fs_watcher.rs:85:34

2026-08-23T11:42:56+02:00 INFO  [zed::reliability::hang_detection::logging] Background hang detected on Unknown:
Tasks(s) that ran too long
18.155837042s        - crates/fs/src/fs_watcher.rs:85:34

2026-08-23T11:42:56+02:00 INFO  [zed::reliability::hang_detection::logging] Background hang detected on Unknown:
Tasks(s) that ran too long
18.156099417s        - crates/fs/src/fs_watcher.rs:85:34

2026-08-23T11:42:56+02:00 INFO  [zed::reliability::hang_detection::logging] Background hang detected on Unknown:
Tasks(s) that ran too long
18.155881292s        - crates/fs/src/fs_watcher.rs:85:34

2026-08-23T11:42:56+02:00 INFO  [zed::reliability::hang_detection::logging] Background hang detected on Unknown:
Tasks(s) that ran too long
18.15603025s         - crates/fs/src/fs_watcher.rs:85:34

2026-08-23T11:42:56+02:00 INFO  [zed::reliability::hang_detection::logging] Background hang detected on Unknown:
Tasks(s) that ran too long
18.155880042s        - crates/fs/src/fs_watcher.rs:85:34
```

## Solution

My solution is to unblock the blocking code so that it doesn't hang a
background thread whenever the filesystem is slow to respond. The task
poll now returns pending while the syscall runs on the blocking pool, so
other tasks can be polled in the meantime.

## Testing

Behavior is unchanged, so just testing if Zed still picks up created
directories/files should be enough.

## Self-Review Checklist:

- [x] I've reviewed my own diff for quality, security, and reliability
- [x] Unsafe blocks (if any) have justifying comments
- [x] The content adheres to Zed's UI standards
([UX/UI](https://github.com/zed-industries/zed/blob/main/CONTRIBUTING.md#uiux-checklist)
and
[icon](https://github.com/zed-industries/zed/blob/main/crates/icons/README.md)
guidelines)
- [ ] Tests cover the new/changed behavior
- [x] Performance impact has been considered and is acceptable

---

Release Notes:

- Improved responsiveness when watching paths on slow or unresponsive
filesystems

---------

Co-authored-by: Ben Kunkle <ben@zed.dev>
2026-09-25 15:03:35 +00:00
…
2026-09-17 09:59:21 +00:00
…
2026-08-28 20:04:24 +00:00
…
…
2026-09-11 09:13:44 +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%