-
-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Helix unable to parse stackTrace response from debugpy (Python DAP) #6265
Comments
There's a TODO for supporting numbers for Line 314 in 3905243
|
I believe I have a fix (will PR) for the "String || Number" problem, but I seem to have a different bug. Could you, @rkshthrmsh, provide your Using the debug config provided by @RmStorm, I get the error In @RmStorm's config, if I replace |
Hi @thomasaarholt, here's my [[language]]
name = "python"
[language.debugger]
name = "debugpy"
transport = "stdio"
command = "python3"
args = ["-m", "debugpy.adapter"]
[[language.debugger.templates]]
name = "source"
request = "launch"
completion = [ { name = "entrypoint", completion = "filename", default = "." } ]
args = { mode = "debug", program = "{0}"} Hardcoding the file name, as you mentioned, did not have any effect for me. The program was still suspended by my terminal, and the terminal still got messed up. I tried providing the full path to the file as well. Was there something else you tried? |
I've opened #7637, since I at least experience the I still get a messed-up terminal when things crash, but if I replace The first error (using
The second error, using
Make sure you are on a new-ish build of helix. You can see the logs using |
Can confirm, though it's only at the beginning. It seems as though Helix was being forcefully suspended with Ctrl+Z, causing some terminals like Kitty to freak out. I then used |
Any update on this? Would love to spend some more time in Helix, but as a Python developer the lack of support for debugpy is holding me back slightly. |
I have the same problem. In the meantime I use helix in combination with the pudb debugger in a tmux session. Works for me quite well. |
Since there was no progress on this issue I proposed my solution for problem with parsing. Helix still breaks terminal on hitting any breakpoint, but I believe this might be one step forward solving underlying issue |
I currently use Helix for my main work, but as I need to debug a lot of python code I have to have Jetbrains in addition. Now I'm struggling with poetry issues due to a Jetbrain bug so I have to do side-IDE hopping to compensate 😄 I'm very interested in this, but I don't know rust. Does anyone know the specific places that has to be changed to support this? Anyone more experienced that knows how we could make it easier for us nuubs to jump in and contribute to this part? Could we instead of supporting ints, just transform integers into strings beforehand somehow? |
While trying to integrate debugpy, it seems that Helix is unable to parse the
stackTrace
response. This is possibly because Helix is attempting to interpretModule.id
and / orStackFrame.moduleId
as a string instead of a number, which is what debugpy returns. The DAP spec recommends either of these types for those fields. Here is a log from Helix:Related issue in debugpy repo: microsoft/debugpy#1227
The text was updated successfully, but these errors were encountered: