Skip to content

Debug configuration when no launch.json exists is still used after launch.json creation #17353

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
luabud opened this issue Sep 9, 2021 · 0 comments · Fixed by #17354
Closed
Assignees
Labels
area-debugging bug Issue identified by VS Code Team member as probable bug

Comments

@luabud
Copy link
Member

luabud commented Sep 9, 2021

Environment data

  • VS Code version: 1.60.0
  • Extension version (available under the Extensions sidebar): v2021.9.1218518343
  • OS and version: Windows 10

[NOTE: If you suspect that your issue is related to the Microsoft Python Language Server (python.languageServer: 'Microsoft'), please download our new language server Pylance from the VS Code marketplace to see if that fixes your issue]

Steps to reproduce:

[NOTE: Self-contained, minimal reproducing code samples are extremely helpful and will expedite addressing your issue]

  1. Open a file in a workspace with no launch.json file.
  2. Open the debug window and hit "Run and debug"
  3. Select "Python file"
  4. Now open the debug view again and click "create a launch.json file"
  5. Select a different config (e.g. Flask)
  6. Start debugging with that configuration
  7. See that it will keep using the previous configuration (for running and debugging)
@luabud luabud added bug Issue identified by VS Code Team member as probable bug triage-needed Needs assignment to the proper sub-team area-debugging needs PR and removed triage-needed Needs assignment to the proper sub-team labels Sep 9, 2021
@github-actions github-actions bot added the triage-needed Needs assignment to the proper sub-team label Sep 9, 2021
@karthiknadig karthiknadig removed the triage-needed Needs assignment to the proper sub-team label Sep 9, 2021
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Dec 4, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-debugging bug Issue identified by VS Code Team member as probable bug
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants