microsoft / microsoft/vscode-python-debugger

[BUG] Debugging with purpose ignored in user/workspace settings.

Open
#525 5 comments 6 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug needs PR
Dominant language
TypeScript
Stars
181
Forks
126
Avg merge
2d 3h
Merged PRs (30d)
3

Description

Environment data

  • VS Code version: v1.60.0
  • Extension version (available under the Extensions sidebar): v2021.9.1246542782
  • OS and version: win10 20h2 64bit
  • Python version (& distribution if applicable, e.g. Anaconda): py3.7.7 32bit
  • Type of virtual environment used (N/A | venv | virtualenv | conda | ...): `N/A
  • Relevant/affected Python packages and their versions: pylance v2021.9.4, jupyter v2021.8.2041215044
  • Value of the python.languageServer setting: Default

Steps to reproduce:

  1. add this configuration in workspace/user settings:
    "launch": {
        "version": "0.2.0",
        "configurations": [
            {
                "name": "Python: Current File - Editor button",
                "type": "python",
                "request": "launch",
                "program": "${file}",
                "console": "integratedTerminal",
                "justMyCode": false,
                "purpose": ["debug-in-terminal"]
            }
        ]
    }
  1. try debug from editor button, it doesn't work. but in folder launch.json it works.

Logs

EMPTY

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the editor-button launch using the workspace/user settings configuration, then compare it with the folder launch.json configuration where it works. Trace how the debugger extension handles the purpose field in each path; done means purpose ["debug-in-terminal"] is honored from workspace and user settings.

Written by the indexing model from the issue text.

Assessment

Tech stack
python, typescript, vscode
Domain
devtools
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.