nix-community / home-manager

Manage a user environment using Nix [maintainer=@rycee]
https://nix-community.github.io/home-manager/
MIT License
6.8k stars 1.78k forks source link

bug: vscode python debugging neither working for scripts nor pytest tests #5193

Open robert-elles opened 6 months ago

robert-elles commented 6 months ago

Are you following the right branch?

Is there an existing issue for this?

Issue description

Hi, I cannot debug python scripts or pytest tests with vscode. On clicking the debug icon on the pystest test I get a message saying debug stopped. I can click open launch.json. In the testing tab the icon keeps spinning indicating that something is still running. I don't see any error messages in none of the output channels.

launch.json contains the following:

 "version": "0.2.0",
  "configurations": [
    {
      "name": "Python Debugger: Remote Attach",
      "type": "debugpy",
      "request": "attach",
      "connect": { "host": "localhost", "port": 5678 },
      "pathMappings": [{ "localRoot": "${workspaceFolder}", "remoteRoot": "." }]
    },
    {
      "name": "Python Debugger: Current File",
      "type": "debugpy",
      "request": "launch",
      "program": "${file}",
      "console": "integratedTerminal"
    },
    {
      "name": "Python: Debug Tests",
      "type": "debugpy",
      "request": "launch",
      "program": "${file}",
      "purpose": ["debug-test"],
      "console": "integratedTerminal",
      "module": "pytest",
      "justMyCode": false
    }
  ]
}

I have vscode installed via home manager like so:

  home-manager = {
    users.robert = {
      programs.vscode = {
        enable = true;
        # package = pkgs.vscode.fhs;
        package = pkgs.vscode.fhsWithPackages (ps: with ps; [ python311Packages.debugpy ]);
        extensions = with pkgs.vscode-extensions;
          [
            ms-python.python
            ms-python.vscode-pylance
            ms-pyright.pyright
          ];
      };
    };
  };

}

Maintainer CC

No response

System information

- system: `"x86_64-linux"`
 - host os: `Linux 6.8.0-zen1, NixOS, 24.05 (Uakari), 24.05pre-git`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.18.2`
 - channels(root): `"nixos-23.05"`
 - nixpkgs: `/nix/store/amxd2p02wx78nyaa4bkb0hjvgwhz1dq7-source`
stale[bot] commented 3 months ago

Thank you for your contribution! I marked this issue as stale due to inactivity. Please be considerate of people watching this issue and receiving notifications before commenting 'I have this issue too'. We welcome additional information that will help resolve this issue. Please read the relevant sections below before commenting.

If you are the original author of the issue

* If this is resolved, please consider closing it so that the maintainers know not to focus on this. * If this might still be an issue, but you are not interested in promoting its resolution, please consider closing it while encouraging others to take over and reopen an issue if they care enough. * If you know how to solve the issue, please consider submitting a Pull Request that addresses this issue.

If you are not the original author of the issue

* If you are also experiencing this issue, please add details of your situation to help with the debugging process. * If you know how to solve the issue, please consider submitting a Pull Request that addresses this issue.

Memorandum on closing issues

Don't be afraid to manually close an issue, even if it holds valuable information. Closed issues stay in the system for people to search, read, cross-reference, or even reopen – nothing is lost! Closing obsolete issues is an important way to help maintainers focus their time and effort.