-
Notifications
You must be signed in to change notification settings - Fork 138
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
Meaning of "restart" in "disconnect" and "terminate" events #74
Comments
Yes, this is a bit unclear for me too. I am currently ignoring -- it never seems to be true -- probably because my extension supports a restart. I have a feeling that for extensions that don't support a restart request, a disconnect is called first before a full restart happens |
"restart sequence" means: For the "launch" case "restart" can be used to pickup source changes that are not automatically picked up while the program is running. For the "attach" case "restart" has no direct effect on the debug target because the debug target continues running. But it still might have an effect on debugging because the debug adapter is restarted and this could pick up changes to files that the debug adapter uses, e.g. source maps. |
Wouldn't initialize (plus potentially more requests depending on how initialize event is implemented, see https://microsoft.github.io/debug-adapter-protocol/overview) be part of the restart sequence? Would the restart sequence happen only if |
The spec just says:
It is not clear what this means, exactly - the term restart sequence is not defined anywhere. It seems like it is connected in some way to "restart" request, but it's not clear how they all interact.
(#73 is possibly related)
The text was updated successfully, but these errors were encountered: