Using vscode-js-debug
debug adapter fails due to unimplemented startDebugging
reverse request
#11906
Labels
C-bug
Category: This is a bug
Summary
This is something of a continuation of #4214
I am attempting to use the vscode-js-debug debugger adapter to debug typescript applications within Helix. It became independently useable by compliant editors starting in September 2023: microsoft/vscode-js-debug#926
Briefly after launching a debug session, the adapter will send a
startDebugging
command to Helix. This is not currently handled by Helix and after this point the editor and adapter are effectively placed into an invalid state where debugger related Helix commands are nonfunctional.Reproduction Steps
languages.toml
I tried this:
echo 'console.debug("hello world")' > /tmp/index.ts
wget 'https://github.com/microsoft/vscode-js-debug/releases/download/v1.94.0/js-debug-dap-v1.94.0.tar.gz' -O /tmp/js-debug-dap.tar.gz
tar -xvzf /tmp/js-debug-dap.tar.gz
languages.toml
configuration to~/.config/helix/languages.toml
hx /tmp/index.ts
<space>Gbl<return>index.ts<return><esc>
I expected this to happen:
Helix should properly reflect the state of the debugger and correctly pass along debugger control commands such as
:dap_next
.Instead, this happened:
Helix does not recognize that the debugger is paused and waiting for remote control. Helix commands associated with debugging do not function due to the editor/adaptor state mismatch.
Helix log
~/.cache/helix/helix.log
Platform
Linux
Terminal Emulator
wezterm c26b6a3
Installation Method
nixpkgs
Helix Version
helix 24.7 (079f544)
The text was updated successfully, but these errors were encountered: