Conrad Irwin
bfe4c40f73
This reverts commit 391eb380b59d5b36efdea027bfdb2fc4f55f4ad0. For some reason that is very unclear to me, this broke ssh'ing into macOS remotes. The remote process aborts with: ``` ------------------------------------- Translated Report (Full Report Below) ------------------------------------- Process: zed-remote-server-dev-build [78088] Path: /Users/USER/*/zed-remote-server-dev-build Identifier: zed-remote-server-dev-build Version: ??? Code Type: ARM-64 (Native) Parent Process: launchd [1] Responsible: iTerm2 [62245] User ID: 501 Date/Time: 2025-03-13 19:30:37.6827 -0600 OS Version: macOS 15.3.1 (24D70) Report Version: 12 Anonymous UUID: 3A9631EB-5468-8CA4-7A0F-E36C3FF9D04F Sleep/Wake UUID: C935AE4C-E06A-4F6D-BE97-101E4E03482F Time Awake Since Boot: 910000 seconds Time Since Wake: 1265 seconds System Integrity Protection: enabled Crashed Thread: 0 Dispatch queue: com.apple.main-thread Exception Type: EXC_CRASH (SIGABRT) Exception Codes: 0x0000000000000000, 0x0000000000000000 Termination Reason: Namespace OBJC, Code 1 Application Specific Information: crashed on child side of fork pre-exec Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 libsystem_kernel.dylib 0x18653fc6c __abort_with_payload + 8 1 libsystem_kernel.dylib 0x186565eb8 abort_with_payload_wrapper_internal + 104 2 libsystem_kernel.dylib 0x186565e50 abort_with_reason + 32 3 libobjc.A.dylib 0x1861dc040 _objc_fatalv(unsigned long long, unsigned long long, char const*, char*) + 128 4 libobjc.A.dylib 0x1861dbfc0 _objc_fatal(char const*, ...) + 44 5 libobjc.A.dylib 0x1861c1674 performForkChildInitialize(objc_class*, objc_class*) + 400 6 libobjc.A.dylib 0x1861a67f0 initializeNonMetaClass + 592 7 libobjc.A.dylib 0x1861c4a3c initializeAndMaybeRelock(objc_class*, objc_object*, locker_mixin<lockdebug::lock_mixin<objc_lock_base_t>>&, bool) + 164 8 libobjc.A.dylib 0x1861a5f98 lookUpImpOrForward + 304 9 libobjc.A.dylib 0x1861a5b84 _objc_msgSend_uncached + 68 10 zed-remote-server-dev-build 0x104f9ec4c _$LT$$LP$$RP$$u20$as$u20$objc..message..MessageArguments$GT$::invoke::hf68c58806f4b5702 + 56 11 zed-remote-server-dev-build 0x104f9d4c8 objc::message::platform::send_unverified::h2ec8392957fd6551 + 120 12 zed-remote-server-dev-build 0x104e5631c cocoa::appkit::NSPasteboard::generalPasteboard::h68122d7f32549cba + 512 13 zed-remote-server-dev-build 0x104e3b3b4 gpui::platform::mac::platform::MacPlatform::new::hb68d7ae2c5fdea7e + 336 14 zed-remote-server-dev-build 0x104e48008 gpui::platform::current_platform::h931999673c8c6468 + 28 15 zed-remote-server-dev-build 0x104ee4284 gpui::app::Application::headless::h3bffec62c65240ce + 32 16 zed-remote-server-dev-build 0x1023746ac remote_server::unix::execute_run::h7ac8de1a7e257f61 + 1200 17 zed-remote-server-dev-build 0x102368e1c remote_server::main::h42e4b18462b32dcf + 252 (main.rs:56) 18 zed-remote-server-dev-build 0x10236717c core::ops::function::FnOnce::call_once::h8534244cea12c898 + 16 (function.rs:250) 19 zed-remote-server-dev-build 0x102368154 std::sys::backtrace::__rust_begin_short_backtrace::h22fd48e0f46eb10b + 12 (backtrace.rs:152) 20 zed-remote-server-dev-build 0x10236bf74 std::rt::lang_start::_$u7b$$u7b$closure$u7d$$u7d$::hf8bd0081bf8d785b + 16 (rt.rs:195) 21 zed-remote-server-dev-build 0x105723d20 std::rt::lang_start_internal::h5f91760815528aa2 + 1092 22 zed-remote-server-dev-build 0x10236bf50 std::rt::lang_start::hb88fe48ac1498ea6 + 60 (rt.rs:194) 23 zed-remote-server-dev-build 0x10236b67c main + 36 24 dyld 0x1861f4274 start + 2840 ``` Which is not even (apparently) on the line that calls this function. To reproduce this, run `ZED_BUILD_REMOTE_SERVER=true cargo run ssh://127.0.0.1/~/`. 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.