Michael Sloan
ca6825066f
Also renamed the repo to `livekit-rustk-sdks` on GitHub for clarity. The old name will still work for old references. See [discussion here](https://github.com/zed-industries/zed/pull/21292#issuecomment-2529573128). The only changes in the target repo are immaterial: ``` $ git diff 799f10133d93ba2a88642cd480d01ec4da53408c 060964da10574cd9bf06463a53bf6e0769c5c45e diff --git a/livekit-protocol/src/livekit.rs b/livekit-protocol/src/livekit.rs index 43f5496..19181c2 100644 --- a/livekit-protocol/src/livekit.rs +++ b/livekit-protocol/src/livekit.rs @@ -3837,7 +3837,7 @@ pub struct SendDataRequest { #[prost(string, optional, tag="5")] pub topic: ::core::option::Option<::prost::alloc::string::String>, } - +/// #[allow(clippy::derive_partial_eq_without_eq)] #[derive(Clone, PartialEq, ::prost::Message)] pub struct SendDataResponse { diff --git a/livekit-runtime/Cargo.toml b/livekit-runtime/Cargo.toml index 4d83cdf..7051f30 100644 --- a/livekit-runtime/Cargo.toml +++ b/livekit-runtime/Cargo.toml @@ -7,6 +7,7 @@ edition = "2021" repository = "https://github.com/livekit/rust-sdks" [features] +tokio = ["dep:tokio", "dep:tokio-stream"] async = ["dep:async-std", "dep:futures", "dep:async-io"] dispatcher = ["dep:futures", "dep:async-io", "dep:async-std", "dep:async-task"] ``` Release Notes: - N/A
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.