Om Chillure
d06406f7d8
## Summary When `debugger::Start` runs a build task (via the `"build"` field in `debug.json`), it was bypassing the task's `"save"` property and calling `project.create_terminal_task()` directly. This meant unsaved files were never saved before the build ran, even when `"save": "all"` was set unlike `task: spawn` which correctly saved first. **Changes:** - Extracted `Workspace::save_for_task(workspace, strategy, cx)` as a shared async helper in `workspace/src/tasks.rs` - Refactored `schedule_resolved_task` to call this helper (no behavior change, removes inline duplication) - Called the same helper in `RunningState::resolve_scenario` before `create_terminal_task`, so the debugger build path now respects the task's `save` strategy - Added `test_save_for_task_all`, `test_save_for_task_current`, and `test_save_for_task_none` tests covering the extracted helper directly ## Self-Review Checklist - [x] I've reviewed my own diff for quality, security, and reliability - [ ] Unsafe blocks (if any) have justifying comments - [x] The content is consistent with the [UI/UX checklist](https://github.com/zed-industries/zed/blob/main/CONTRIBUTING.md#uiux-checklist) - [x] Tests cover the new/changed behavior - [x] Performance impact has been considered and is acceptable Closes #53284 ## Video after fix [Screencast from 2026-04-08 08-04-18.webm](https://github.com/user-attachments/assets/b0c20164-3670-440a-b43a-8457fb57bfbd) ## Release Notes: - Fixed debugger not saving files before running a build task when `"save": "all"` is set in the task definition
Zed
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:
- Web (tracking issue)
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
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 specifiederror for a crate you've created? If so, addpublish = falseunder[package]in your crate's Cargo.toml. - Is the error
failed to satisfy license requirementsfor 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 theacceptedarray inscript/licenses/zed-licenses.toml. - Is
cargo-aboutunable to find the license for a dependency? If so, add a clarification field at the end ofscript/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.