-
Notifications
You must be signed in to change notification settings - Fork 25
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
debug: Indefinitely stuck in dape:starting
#172
Comments
I don't know, sorry. I don't use dape (yet...). @iNecas, any ideas? |
There are still some changes to make it working end2end, I first was working with the changes in the DebugAdapter julia-vscode/DebugAdapter.jl#95. During the review, it seems like it's better place to make the corresponding changes in he dape itself (there are some incompatibilities when it comes to passing null values). So short time solution would be to use local DebugAdapter with the patches applied. The proper solution would be to make corresponding changes in dape, but unfortunately I don't have capacity now to work on those. |
I can verifify that this works with the DebugAdapter.jl fork from the PR. It can however lead to an annoying bug. If the first time the extension is loaded is with Julia < 1.11, then the wrongly resolved For reference, the new Project.toml would look like this:
|
Another possibility is to monkey-patch DebugAdapter from the extension itself. (i.e. check the installed version of DebugAdapter, and if it’s affected, dynamically replace the affected code.) |
Thanks for adding the new DebugAdapter.jl integration with dape.
Unfortunately, I can't get it to work -- the dape UI windows open, but then I am indefinitely stuck at status
dape:starting
. I have already set thedape-request-timeout
to 120 seconds, because sometimes Julia needs to still compile something. However, it doesn't seem to help.Has anybody had any luck using the new extension?
This is on emacs 30, with julia 1.10, and
Could the problem be related to the json parser changes in emacs 30?
The text was updated successfully, but these errors were encountered: