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

Python debugging not working #7927

Closed
gmikhail opened this issue Oct 11, 2019 · 4 comments
Closed

Python debugging not working #7927

gmikhail opened this issue Oct 11, 2019 · 4 comments
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug info-needed Issue requires more information from poster

Comments

@gmikhail
Copy link

Issue Type: Bug

When I press debug button (or F5) - nothing happened. No Terminal or Debug Console output. Even no errors message. Debug overlay flashes and that's it.

Also shortcut Ctrl+F5 (start without debugging) not working as expected (debug overlay flashes, but file not executed), but when I press "Run Python File in Terminal" button, it works. Am I misunderstanding something? What is the keyboard shortcut for "Run" button, then?

Previously, debugging worked on this computer. Problems started after update. Unfortunately, I have not updated for a long time, therefore I can’t say specifically with which version everything broke.

My launch.json

{
    // Use IntelliSense to learn about possible attributes.
    // Hover to view descriptions of existing attributes.
    // For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
    "version": "0.2.0",
    "configurations": [
        {
            "name": "Python: Текущий файл",
            "type": "python",
            "request": "launch",
            "program": "${file}",
            "console": "integratedTerminal"
        }
    ]
}

I don’t know for sure this is an extension bug or VS Code. Please, move the issue to the appropriate place, if nessesary.

Extension version: 2019.10.41019
VS Code version: Code 1.39.1 (88f15d17dca836346e787762685a40bb5cce75a8, 2019-10-10T23:31:28.683Z)
OS version: Windows_NT x64 10.0.18362

System Info
Item Value
CPUs Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz (8 x 2808)
GPU Status 2d_canvas: enabled
flash_3d: enabled
flash_stage3d: enabled
flash_stage3d_baseline: enabled
gpu_compositing: enabled
multiple_raster_threads: enabled_on
native_gpu_memory_buffers: disabled_software
oop_rasterization: disabled_off
protected_video_decode: unavailable_off
rasterization: enabled
skia_deferred_display_list: disabled_off
skia_renderer: disabled_off
surface_synchronization: enabled_on
video_decode: enabled
viz_display_compositor: disabled_off
webgl: enabled
webgl2: enabled
Load (avg) undefined
Memory (System) 15.89GB (9.39GB free)
Process Argv
Screen Reader no
VM 0%
@ghost ghost added the triage-needed Needs assignment to the proper sub-team label Oct 11, 2019
@gmikhail gmikhail changed the title Pythod debug not working Pythod debugging not working Oct 11, 2019
@gmikhail gmikhail changed the title Pythod debugging not working Python debugging not working Oct 11, 2019
@andrew-buckley
Copy link

This has also suddenly started happening on my machine as well. Updated to the latest extension version as of 10 minutes ago.

@karthiknadig
Copy link
Member

@andrew-buckley @gmikhail it is highly likely this issue #7836 . We are working on providing a fix for this. Meanwhile if you need a workaround see here: #7836 (comment)

@karthiknadig karthiknadig self-assigned this Oct 11, 2019
@ghost ghost removed the triage-needed Needs assignment to the proper sub-team label Oct 11, 2019
@karthiknadig karthiknadig added info-needed Issue requires more information from poster bug Issue identified by VS Code Team member as probable bug labels Oct 11, 2019
@gmikhail
Copy link
Author

Thank you @karthiknadig, workaround works.

@karthiknadig
Copy link
Member

@gmikhail Thanks for confirming, closing this since this is tracked via #7836

@ghost ghost removed the triage label Oct 11, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Oct 18, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue identified by VS Code Team member as probable bug info-needed Issue requires more information from poster
Projects
None yet
Development

No branches or pull requests

3 participants