Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
Add DA and ptvsd experiments support to remote debugging API #7570
Add DA and ptvsd experiments support to remote debugging API #7570
Changes from 4 commits
82effe5
40b9573
11c2d0a
dc7b63d
98a3de5
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
From what I understand, the
await debugFactory.useNewPtvsd(pythonSettings.pythonPath))
case is for when a user is using their own ptvsd. If that's the case then won't that case still apply after the experiment is over? We would be stuck still depending on the old debug adapter code (e.g.RemoteDebuggerExternalLauncherScriptProvider
).So this is probably the best opportunity to address that. Do that by folding
RemoteDebuggerExternalLauncherScriptProvider
intogetRemoteLauncherCommand()
here or intoDebugAdapterDescriptorFactory.getPtvsdPath()
.I suppose we could also punt on it (open a new issue). :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Anyway, the key question is whether or not the user gets a version of ptvsd that has the new debug adapter. Really the key question is which "script" to use. So it may make more sense to have
DebugAdapterDescriptorFactory.getPtvsdPath()
deal with the cases. ThenDebugAdapterDescriptorFactory.useNewPtvsd()
would be unnecessary. That would meangetRemoteLauncherCommand()
would look more like this:DebugAdapterDescriptorFactory.getPtvsdPath()
would have to deal with the 3 cases (new debug adapter, old debug adapter with our distributed ptvsd, user-installed ptvsd).FWIW, I'm also not a fan of how ptvsd-specific details are sitting in this module. They should be with the other debugger stuff. The above helps address that a little. I'd expect a better solution to involve adding something like
DebugAdapterDescriptorFactory.getPTVSDArgv()
. We can look into addressing this separately. :)