Skip to content

The order in which the terminal starts the conda environment during debugging #5867

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

Closed
skywolf123 opened this issue May 31, 2019 · 2 comments

Comments

@skywolf123
Copy link

Issue Type: Bug

In the anaconda environment, press F5 to start debugging, but the error "DLL load failed" seems to be that the debugging terminal failed to start the conda environment at the first startup, but first executed the python code and then tried "conda activate base".

VS Code version: Code 1.34.0 (a622c65b2c713c890fcf4fbf07cf34049d5fe758, 2019-05-15T21:59:37.030Z)
OS version: Windows_NT x64 10.0.17763

System Info
Item Value
CPUs Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz (4 x 2712)
GPU Status 2d_canvas: enabled
checker_imaging: disabled_off
flash_3d: enabled
flash_stage3d: enabled
flash_stage3d_baseline: enabled
gpu_compositing: enabled
multiple_raster_threads: enabled_on
native_gpu_memory_buffers: disabled_software
rasterization: enabled
surface_synchronization: enabled_on
video_decode: enabled
webgl: enabled
webgl2: enabled
Load (avg) undefined
Memory (System) 7.91GB (2.62GB free)
Process Argv
Screen Reader no
VM 67%
Extensions (4)
Extension Author (truncated) Version
vscode-language-pack-zh-hans MS- 1.34.2
anaconda-extension-pack ms- 1.0.1
python ms- 2019.5.17059
vscode-yaml red 0.4.1

(1 theme extensions excluded)

@ghost ghost added the triage-needed Needs assignment to the proper sub-team label May 31, 2019
@skywolf123
Copy link
Author

image

@DonJayamanne
Copy link

Duplicate of #5664

@DonJayamanne DonJayamanne marked this as a duplicate of #5664 Jun 3, 2019
@ghost ghost removed the triage-needed Needs assignment to the proper sub-team label Jun 3, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Jun 10, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants