You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When starting a debugging session, it will automatically start one terminal, which is not consistent with the terminal that has already been started and set with environment variables.
Extension version: 2024.4.0
VS Code version: Code 1.88.1 (e170252f762678dec6ca2cc69aba1570769a5d39, 2024-04-10T17:41:02.734Z)
OS version: Windows_NT x64 10.0.19045
Modes:
Remote OS version: Linux x64 5.15.0-76-generic
Python version (& distribution if applicable, e.g. Anaconda): 3.11.8
Type of virtual environment used (e.g. conda, venv, virtualenv, etc.): Conda
System Info
Item
Value
CPUs
Intel(R) Core(TM) i7-10850H CPU @ 2.70GHz (12 x 2712)
Thanks for your issue report, that is the default behaviour for the debugger, we are working on a feature to launch the debugger from the terminal, this should be done by the end of June.
Type: Bug
When starting a debugging session, it will automatically start one terminal, which is not consistent with the terminal that has already been started and set with environment variables.
Extension version: 2024.4.0
VS Code version: Code 1.88.1 (e170252f762678dec6ca2cc69aba1570769a5d39, 2024-04-10T17:41:02.734Z)
OS version: Windows_NT x64 10.0.19045
Modes:
Remote OS version: Linux x64 5.15.0-76-generic
canvas_oop_rasterization: enabled_on
direct_rendering_display_compositor: disabled_off_ok
gpu_compositing: enabled
multiple_raster_threads: enabled_on
opengl: enabled_on
rasterization: enabled
raw_draw: disabled_off_ok
skia_graphite: disabled_off
video_decode: enabled
video_encode: enabled
vulkan: disabled_off
webgl: enabled
webgl2: enabled
webgpu: enabled
A/B Experiments
The text was updated successfully, but these errors were encountered: