Skip to content

Debugger not connecting since version 25.0.0 #618

Closed as not planned
Closed as not planned

Description

Whenever I am launching a debug session since the release of version 25.0.0 of the extension, the debugger hangs for ~30s, then I get this popup:

Image

This happens when launching via a launch config or directly launching a file in debug mode.

Reverting to version 24.14.2 of the extension fixes this.

I am on WSL, using a Pixi Python environment.

Here are the Python Debugger logs:

2025-02-18 12:02:20.629 [info] Debugging using the editor button 'Debug in terminal'
2025-02-18 12:02:20.643 [info] Getting configurations for workspace
2025-02-18 12:02:20.645 [info] Using configuration in launch.json
2025-02-18 12:02:20.821 [info] Using workspaceFolder found for the program:  /home/pan/repositories/Booster-AI
2025-02-18 12:02:20.879 [info] Resolving launch configuration with substituted variables
2025-02-18 12:02:20.879 [info] Using workspaceFolder found for the program:  /home/pan/repositories/Booster-AI
2025-02-18 12:02:20.939 [info] DAP Server launched with command: /home/pan/repositories/Booster-AI/.pixi/envs/booster-ai-development/bin/python /home/pan/.vscode-server/extensions/ms-python.debugpy-2025.0.1/bundled/libs/debugpy/adapter
2025-02-18 12:02:21.070 [info] Received 'debugpySockets' event from debugpy.
2025-02-18 12:02:21.075 [info] Received 'debugpySockets' event from debugpy.
2025-02-18 12:02:21.075 [info] Received 'debugpySockets' event from debugpy.

The Python logs:

2025-02-18 12:02:21.143 [info] Not enabling terminal env var experiment in multiroot remote workspaces
2025-02-18 12:02:21.144 [info] Send text to terminal: /home/pan/.pixi/bin/pixi shell --manifest-path /home/pan/repositories/Booster-AI/pixi.toml --environment booster-ai-development
2025-02-18 12:02:21.896 [info] Send text to terminal:  /usr/bin/env /home/pan/repositories/Booster-AI/.pixi/envs/booster-ai-development/bin/python /home/pan/.vscode-server/extensions/ms-python.debugpy-2025.0.1/bundled/libs/debugpy/adapter/../../debugpy/launcher 34449 -- /home/pan/repositories/Booster-AI/project_management/workspace/configurator.py 

Activity

  1. rchiodo commented on Feb 18, 2025

    @rchiodo
    Contributor

    I would hazard a guess this is similar to the problem with this issue: #617

  2. eleanorjboyd commented on Feb 18, 2025

    @eleanorjboyd
    Contributor

    yes good guess Rich Chiodo (@rchiodo)

    Raphaël Melançon (@RaphaelMelanconAtBentley) can you include the launch config you are trying to run with? And the code you are attempting to debug?

  3. RaphaelMelanconAtBentley commented on Feb 19, 2025

    @RaphaelMelanconAtBentley
    Author

    Well, there isn't always a launch config, as it also happens when I simply use this option:

    Image

    And it happens with any code, even this:

    # test_debugger.py
    if __name__ == "__main__":
        print("Hello, world!")

    Might it have something to do with the environment activation in the terminal?
    I have "python.terminal.activateEnvironment": true and "python.terminal.activateEnvInCurrentTerminal": true.

    Here is what the Python Debug Console terminal shows when it is created:

    > /home/pan/.pixi/bin/pixi shell --manifest-path /home/pan/repositories/Booster-AI/pixi.toml --environment booster-ai-development
    > /home/pan/.pixi/bin/pixi shell --manifest-path /home/pan/repositories/Booster-AI/pixi.toml --environment booster-ai-development
     /usr/bin/env /home/pan/repositories/Booster-AI/.pixi/envs/booster-ai-development/bin/python /home/pan/.vscode-server/extensions/ms-python.debugpy-2025.0.1/bundled/libs/debugpy/adapter/../../debugpy/launcher 34863 -- /home/pan/repositories/Booster-AI/test_debugger.py
  4. eleanorjboyd commented on Feb 26, 2025

    @eleanorjboyd
    Contributor

    This should be fixed and be out in the most recent point release of the python debugger extension since it is related to #617 which I fixed. Closing for now but re-comment if not and I can reopen

  5. RaphaelMelanconAtBentley commented on Mar 4, 2025

    @RaphaelMelanconAtBentley
    Author

    I am on the latest (pre-release) version of both the Python and the Python Debugger extensions, and this is still happening.

    Eleanor Boyd (@eleanorjboyd) Please reopen

  6. RaphaelMelanconAtBentley commented on Mar 6, 2025

    @RaphaelMelanconAtBentley
    Author

    Weirdly, I can debug unit test if I use the inline test indicator to debug a test. Bug any other way I tried launching a debugging session results in a hang followed by a timeout error.

  7. 11 remaining items

  8. github-actions commented on Jul 25, 2025

    @github-actions

    Hey Eleanor Boyd (@eleanorjboyd), this issue might need further attention.

    Raphaël Melançon (@RaphaelMelanconAtBentley), you can help us out by closing this issue if the problem no longer exists, or adding more information.

  9. vs-code-engineering commented on Aug 24, 2025

    @vs-code-engineering

    Hey Eleanor Boyd (@eleanorjboyd), this issue might need further attention.

    Raphaël Melançon (@RaphaelMelanconAtBentley), you can help us out by closing this issue if the problem no longer exists, or adding more information.

  10. stevenh commented on Aug 24, 2025

    @stevenh

    Still failing

  11. github-actions commented on Sep 24, 2025

    @github-actions

    Hey Eleanor Boyd (@eleanorjboyd), this issue might need further attention.

    Raphaël Melançon (@RaphaelMelanconAtBentley), you can help us out by closing this issue if the problem no longer exists, or adding more information.

  12. vs-code-engineering commented on Oct 23, 2025

    @vs-code-engineering

    This issue has been closed as it has been labeled with info-needed and has not received the additional information that was requested from the issue author. It has been labeled as info-needed for 14 days.

  13. stevenh commented on Oct 23, 2025

    @stevenh

    You got to hate these bots closing legitimate issues.

  14. stevenh commented on Oct 23, 2025

    @stevenh

    Thanks Eleanor Boyd (@eleanorjboyd) if I can help provide any more information on this which would assist let me know.

  15. eleanorjboyd commented on Oct 28, 2025

    @eleanorjboyd
    Contributor

    Hi! Can you try setting these settings and see if either works:

    1. set python.useEnvironmentsExtension: false
    2. set the above to true, then do python-envs.terminal.autoActivationType: off
  16. vs-code-engineering commented on Nov 4, 2025

    @vs-code-engineering

    Raphaël Melançon (@RaphaelMelanconAtBentley), this issue has been labeled with info-needed and has not received a response. Please provide the additional information that was requested, or this issue will be automatically closed in 7 days.

  17. vs-code-engineering commented on Nov 11, 2025

    @vs-code-engineering

    This issue has been closed as it has been labeled with info-needed and has not received the additional information that was requested from the issue author. It has been labeled as info-needed for 7 days.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

info-neededIssue requires more information from postertriage-neededNeeds assignment to the proper sub-team

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions