-
Notifications
You must be signed in to change notification settings - Fork 752
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: forward initializeRequest to delve dap to verify capabilities #822
Comments
If you launch or attach to delve in or before the initialize request (before the decision to add a thin adapter we considered launching delve in goDebugConfiguration where we have access to the launch attributes), then you can get capabilities in real time. Another option is to leave everything as is, only sending back the most minimal set of capabilities from the thin adapter (e.g. configuration done only), then do the forwarding that the comment talks about and communicate back to the editor what the reality is with Capabilities event. |
Change https://golang.org/cl/268460 mentions this issue: |
Change https://golang.org/cl/290449 mentions this issue: |
The thin dlvDapAdapter2 currently handles
initializeRequest
because delve hasn't beenlaunched yet. Delve will start responding to DAP requests after
launchRequest
is received.This is not ideal - delve should be the one that tells us about its capabilities.
From the current comment:
The text was updated successfully, but these errors were encountered: