01648b9370
This PR integrates Zed's Debugger with the Collab database, enabling Zed to guarantee that clients joining a project with active debug sessions in progress will receive and set up those sessions. * Add test for setting active debug panel items on project join * Add DebuggerSession proto message * Modify debugger session * Get collab server to build * Get collab test to compile * Add proto messages * Set up message handler for get debugger sessions * Send set debug panel requests when handling get debugger sessions msg * Get request to send and set debug panel * Setup ground work for debug sessions collab db table * Set up debug_client table for collab db * Remove up GetDebuggerSession proto request code * Get proto::DebuggerSession during join_project_internal * Remove debug_sessions table from collab db * Add migration for debug_client and fix some bugs * Create dap store event queue for remote daps When creating a project in from_join_project_response(...) the debug panel hasn't been initialized yet so it can't handle dap_store events. The solution to this is creating an event queue that debug panel takes from dap store if it's remote and then handles all the events * Fix debug panel join project during session test * Add debug_panel_items table to collab db * Integrate debug_panel_item table into collab msg handlers * Finialize debug_panel_item table refactor for collab db * Integrate UpdateDebugAdapter RPC with collab DB * Handle ShutdownDebugClient RPC for collab db * Fix clippy
Zed
Welcome to Zed, a high-performance, multiplayer code editor from the creators of Atom and Tree-sitter.
Installation
On macOS and Linux you can download Zed directly or install Zed via your local package manager.
Other platforms are not yet available:
- Windows (tracking issue)
- Web (tracking issue)
Developing Zed
- Building Zed for macOS
- Building Zed for Linux
- Building Zed for Windows
- Running Collaboration Locally
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.