Debugging when connected to remote instance

[garytaylor]

I am a brand new user of zed so of course this could be user error, but I have done a fair bit of research.

I tried zed locally and was able to debug an rspec example - so that is a big tick for me - and it was easy.
But, I always use remote environment, so was excited to find zed also had the ability to connect via ssh - perfect, I use a 'coder' environment and it supports ssh - so I connected - and the ide worked just fine.

But, when I try to debug, I just get

error: RPC request GetDebugAdapterBinary failed: Failed to find a debug adapter

After looking into the source code and having a chat with chatgpt, I came to the conclusion that this only works locally, not remotely ? The extensions directory is empty on the remote side so my guess is the ruby extension was not registering and therefore the extension registry had no debug adapter called 'rdbg'.

Note that I ensured the debug gem was present - for belt and braces, I installed it in the gemfile as well as in the system wide gems - but still nothing.

[ConradIrwin]

@garytaylor This should work (tm); is there anything in your Zed.log?

[garytaylor]

Ill check - but there has been a fix done below - so i might wait until that lands before i try again. Thanks

[osiewicz]

This might be fixed by: #33876 (which should land on Preview and Stable on Wednesday)

[garytaylor]

Thank you - ill try again at the end of the week

[garytaylor]

It is fixed thank you - the only glitch is that the terminal window in the debugger panel doesnt show - so i cant see whats going on, but I have confirmed that it is actually running and I can stop at breakpoints etc..

Im trying to master attaching next - for the cases where i need to see STDOUT - I can only get it working with tcp connection but thats a workaround for now until the terminal window is fixed. I guess its all new so I can't expect perfection :-)

Even when having to fiddle around with workarounds though - loving zed, not going back to rubymine any time soon and definitely not vscode