Skip to content
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

Chosen user-settings debug launch configuration not remembered #129425

Open
bersbersbers opened this issue Jul 26, 2021 · 1 comment
Open

Chosen user-settings debug launch configuration not remembered #129425

bersbersbers opened this issue Jul 26, 2021 · 1 comment
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug debug Debug viewlet, configurations, breakpoints, adapter issues
Milestone

Comments

@bersbersbers
Copy link

I was asked to post this in #124770 (comment).

Does this issue occur when all extensions are disabled?: Yes/No

  • VS Code Version: 1.58.2
  • OS Version: Windows 10, Remote SSH into Linux

Steps to Reproduce:

  1. Have a launch config in your user settings.json (let' say "Python: Current File", which makes sense in any folder or workspace)
  2. Have a project/.vscode/launch.json with additional launch configs (let's call them "A", "B", "C")
  3. Use a multi-root workspace (not sure this is required, maybe you can skip this)
  4. Select "Python: Current File (user settings)" as the current debug config
  5. Reload Window, OR: Change any setting in any of the launch configurations and save.
  6. Note that launch config "A" is selected.

settings.json:

    "launch": {
        "configurations": [
            {
                "presentation": {
                    "group": "00 Python",
                    "order": 0,
                },
                "name": "Python: Current File",
                "type": "python",
                "request": "launch",
                "program": "${file}",
                "justMyCode": false,
                "subProcess": true,
                "internalConsoleOptions": "openOnSessionStart",
                "console": "internalConsole",
            },
        ],
    },

Related issues: #90216, #100451.

@weinand weinand added the debug Debug viewlet, configurations, breakpoints, adapter issues label Jul 26, 2021
@weinand weinand removed their assignment Jul 26, 2021
@isidorn isidorn added the bug Issue identified by VS Code Team member as probable bug label Jul 27, 2021
@isidorn isidorn added this to the Backlog milestone Jul 27, 2021
@isidorn isidorn assigned roblourens and unassigned isidorn Aug 18, 2021
@nmoreaud
Copy link

I see this behavior in 2 cases:

  • Have a workspace + a .vscode/launch.json or a .vscode/settings.json with a launch section (motivation = workaround for a recurrent bug: https://stackoverflow.com/a/76387867/3412316)
  • Have a multiroot workspace + a second project with a .vscode/launch.json or a .vscode/settings.json with a launch section

Ex: If I have this launch config in my workspace:

    "launch": {
        "configurations": [
            {
                "name": "A", 
                "type": "debugpy",
                "request": "launch",  
                "program": "${file}",
                "justMyCode": true 
            },

and this one in a launch.json:

{
    "version": "0.3.0",
    "configurations": [
        {
            "name": "Python: Current File",
            "type": "debugpy",
            "request": "launch",
            "program": "${file}",
        }
    ]
}

If I flip "JustMyCode" boolean, the "Run and Debug" combo box is automatically reset to "Python: Current File".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Issue identified by VS Code Team member as probable bug debug Debug viewlet, configurations, breakpoints, adapter issues
Projects
None yet
Development

No branches or pull requests

5 participants