file path is not clickable when using remote development

[yonchicy]

Check for existing issues

• Completed

Describe the bug / provide steps to reproduce it

cmd + click is not working
file path is not clickable when using remote development. I

Environment

local:
Zed: v0.162.5 (Zed)
OS: macOS 15.1.1
Memory: 16 GiB
Architecture: aarch64

remote:

cat /etc/os-release

NAME="Fedora Linux"
VERSION="41 (Workstation Edition)"
RELEASE_TYPE=stable
ID=fedora
VERSION_ID=41
VERSION_CODENAME=""
PLATFORM_ID="platform:f41"
PRETTY_NAME="Fedora Linux 41 (Workstation Edition)"
ANSI_COLOR="0;38;2;60;110;180"
LOGO=fedora-logo-icon
CPE_NAME="cpe:/o:fedoraproject:fedora:41"
DEFAULT_HOSTNAME="fedora"
HOME_URL="https://fedoraproject.org/"
DOCUMENTATION_URL="https://docs.fedoraproject.org/en-US/fedora/f41/system-administrators-guide/"
SUPPORT_URL="https://ask.fedoraproject.org/"
BUG_REPORT_URL="https://bugzilla.redhat.com/"
REDHAT_BUGZILLA_PRODUCT="Fedora"
REDHAT_BUGZILLA_PRODUCT_VERSION=41
REDHAT_SUPPORT_PRODUCT="Fedora"
REDHAT_SUPPORT_PRODUCT_VERSION=41
SUPPORT_END=2025-05-13
VARIANT="Workstation Edition"
VARIANT_ID=workstation

If applicable, add mockups / screenshots to help explain present your vision of the feature

2024-11-22.18.50.26.mov

If applicable, attach your Zed.log file to this issue.

Zed.log remote

{"level":1,"module_path":"worktree","file":"crates/worktree/src/worktree.rs","line":3791,"message":"(remote server) ignoring event \"/home/yonchicy/.zsh_history.LOCK\" outside of root path \"/home/yonchicy/carolcc\""}
{"level":1,"module_path":"worktree","file":"crates/worktree/src/worktree.rs","line":3791,"message":"(remote server) ignoring event \"/home/yonchicy/.zsh_history.LOCK\" outside of root path \"/home/yonchicy/carolcc\""}
{"level":1,"module_path":"remote::ssh_session","file":"crates/remote/src/ssh_session.rs","line":2143,"message":"(remote server) server:error handling message. type:BlameBuffer, error:unknown buffer id 4294967311"}
{"level":1,"module_path":"remote_server::unix","file":"crates/remote_server/src/unix.rs","line":343,"message":"(remote server) failed to write stdout message: Broken pipe (os error 32)"}
{"level":1,"module_path":"remote_server::unix","file":"crates/remote_server/src/unix.rs","line":343,"message":"(remote server) failed to write stdout message: Broken pipe (os error 32)"}
{"level":1,"module_path":"remote::ssh_session","file":"crates/remote/src/ssh_session.rs","line":2143,"message":"(remote server) server:error handling message. type:BlameBuffer, error:Failed to blame \"a.cc\": git blame process failed: 致命错误：no such path 'a.cc' in HEAD"}
{"level":1,"module_path":"remote::ssh_session","file":"crates/remote/src/ssh_session.rs","line":2143,"message":"(remote server) server:error handling message. type:BlameBuffer, error:Failed to blame \"a.cc\": git blame process failed: 致命错误：no such path 'a.cc' in HEAD"}
{"level":1,"module_path":"remote::ssh_session","file":"crates/remote/src/ssh_session.rs","line":2143,"message":"(remote server) server:error handling message. type:BlameBuffer, error:Failed to blame \"a.cc\": git blame process failed: 致命错误：no such path 'a.cc' in HEAD"}
{"level":1,"module_path":"remote::ssh_session","file":"crates/remote/src/ssh_session.rs","line":2143,"message":"(remote server) server:error handling message. type:BlameBuffer, error:Failed to blame \"a.cc\": git blame process failed: 致命错误：no such path 'a.cc' in HEAD"}
{"level":1,"module_path":"remote::ssh_session","file":"crates/remote/src/ssh_session.rs","line":2143,"message":"(remote server) server:error handling message. type:BlameBuffer, error:Failed to blame \"a.cc\": git blame process failed: 致命错误：no such path 'a.cc' in HEAD"}

Zed.log local

2024-11-22T18:45:36.951685+08:00 [ERROR] server shut down
2024-11-22T18:49:25.950188+08:00 [ERROR] (remote server) server:error handling message. type:BlameBuffer, error:Failed to blame "a.cc": git blame process failed: 致命错误：no such path 'a.cc' in HEAD
2024-11-22T18:49:25.950915+08:00 [ERROR] failed to get git blame data: RPC request BlameBuffer failed: Failed to blame "a.cc": git blame process failed: 致命错误：no such path 'a.cc' in HEAD
2024-11-22T18:49:27.488676+08:00 [ERROR] (remote server) server:error handling message. type:BlameBuffer, error:Failed to blame "a.cc": git blame process failed: 致命错误：no such path 'a.cc' in HEAD
2024-11-22T18:49:27.491766+08:00 [ERROR] failed to get git blame data: RPC request BlameBuffer failed: Failed to blame "a.cc": git blame process failed: 致命错误：no such path 'a.cc' in HEAD
2024-11-22T18:49:33.985541+08:00 [ERROR] (remote server) server:error handling message. type:BlameBuffer, error:Failed to blame "a.cc": git blame process failed: 致命错误：no such path 'a.cc' in HEAD
2024-11-22T18:49:33.991531+08:00 [ERROR] failed to get git blame data: RPC request BlameBuffer failed: Failed to blame "a.cc": git blame process failed: 致命错误：no such path 'a.cc' in HEAD
2024-11-22T18:49:40.069214+08:00 [ERROR] error sending request for url (https://api.zed.dev/telemetry/events?)

Caused by:
    0: client error (SendRequest)
    1: connection error
    2: peer closed connection without sending TLS close_notify: https://docs.rs/rustls/latest/rustls/manual/_03_howto/index.html#unexpected-eof
2024-11-22T18:49:47.215194+08:00 [ERROR] (remote server) server:error handling message. type:BlameBuffer, error:Failed to blame "a.cc": git blame process failed: 致命错误：no such path 'a.cc' in HEAD
2024-11-22T18:49:47.215344+08:00 [ERROR] failed to get git blame data: RPC request BlameBuffer failed: Failed to blame "a.cc": git blame process failed: 致命错误：no such path 'a.cc' in HEAD
2024-11-22T18:52:24.634011+08:00 [ERROR] (remote server) server:error handling message. type:BlameBuffer, error:Failed to blame "a.cc": git blame process failed: 致命错误：no such path 'a.cc' in HEAD
2024-11-22T18:52:24.634551+08:00 [ERROR] failed to get git blame data: RPC request BlameBuffer failed: Failed to blame "a.cc": git blame process failed: 致命错误：no such path 'a.cc' in HEAD