Skip to content

Iterate on remember debug configuration experiment #17195

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

Closed
3 tasks done
luabud opened this issue Sep 1, 2021 · 1 comment
Closed
3 tasks done

Iterate on remember debug configuration experiment #17195

luabud opened this issue Sep 1, 2021 · 1 comment
Assignees
Labels
area-editor-* User-facing catch-all feature-request Request for new features or functionality verified Verification succeeded

Comments

@luabud
Copy link
Member

luabud commented Sep 1, 2021

Right now every time users try to debug a Python file or project (by hitting F5 or click on the "Run and Debug" button in the run and debug window) and they don't have a launch.json file, they are displayed with a configuration prompt asking them what kind of project they want to debug (e.g. Python file, module, Django, Flask, FastAPI, etc.). This is displayed before every debugger run, which can be a quite annoying experience. With this experiment, the debugger will reuse the first selection the user made for the rest of the session.
We're running this as an experiment to validate whether this is indeed an improvement to the debugging experience for all kinds of users, and to evaluate if we're introducing any bugs unintentionally.

  • Ramp up experiment on insiders to 100% of users
  • Ramp up experiment on stable to 50% of users
  • Evaluate whether we will ship it to 100% or if we will iterate on it
@luabud luabud added feature-request Request for new features or functionality triage-needed Needs assignment to the proper sub-team labels Sep 1, 2021
@luabud luabud self-assigned this Sep 1, 2021
@luabud luabud added this to the September 2021 milestone Sep 1, 2021
@luabud luabud added area-editor-* User-facing catch-all needs PR and removed triage-needed Needs assignment to the proper sub-team labels Sep 1, 2021
@luabud luabud changed the title Iterate remember debug configuration experiment Iterate on remember debug configuration experiment Sep 1, 2021
@luabud luabud closed this as completed Sep 28, 2021
@luabud luabud added the verification-needed Verification of issue is requested label Sep 28, 2021
@luabud
Copy link
Member Author

luabud commented Sep 28, 2021

To verify, open a Python file (it can be one that only has print("hello!") in it, hit F5 and select "Python file" from the configuration drop down that will show up (make sure you have no Python config in a launch.json)
Then hit F5 again - you should not see the configuration drop down again as it should reuse the same configuration.

@aeschli aeschli added verified Verification succeeded and removed verification-needed Verification of issue is requested labels Sep 29, 2021
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Dec 1, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-editor-* User-facing catch-all feature-request Request for new features or functionality verified Verification succeeded
Projects
None yet
Development

No branches or pull requests

2 participants