Debugger: Debugger over Remote Development

[helman44]

Summary

So, I have what I hope is a pretty elementary issue. My main concern is the performance of using the Zed debugger (debugpy) over remote development (SSH) on Zed. I am remoting into a RHEL machine from MacOS and have had no issues using Zed up until this point for remote development. I am simply trying to use the new debugger feature with a custom config I created (.zed/debug.json shown below). If I attempt to run the debugger using this config it simply results in an empty debugger pane with a loading circle spinning next to the label. If you have any insights that would be greatly appreciated.

e.g.

press F4
click Debug tab
click RunMyScript
Debug pane pops up and a tiny wheel churns next to RunMyScript infinitely

.zed/debug.json (below)
[
{
"label": "RunMyScript",
"adapter": "Debugpy",
"program": "path/to/my/script.py",
"request": "launch",
"args": [],
"redirectOutput": true,
"stopOnEntry": false,
"subProcess": true,
"cwd": "${ZED_WORKTREE_ROOT}",
"pythonPath": "path/to/my/venv/bin/python"
}
]

Zed Version and System Specs

LOCAL
Zed: v0.190.4 (Zed)
OS: macOS 15.5.0
Memory: 32 GiB
Architecture: aarch64

REMOTE
OS: RHEL 9.4
Memory: 512 GiB
Architecture: x86_64

[ConradIrwin]

It looks like we're not properly inheriting the environment over SSH. In 0.191, I think the infinite spinner should be fixed, but now you'll see an error instead of it just working.

Taking a look at wiring that up properly.