forked from DonJayamanne/pythonVSCode
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Closed
Labels
area-environmentsFeatures relating to handling interpreter environmentsFeatures relating to handling interpreter environmentsbugIssue identified by VS Code Team member as probable bugIssue identified by VS Code Team member as probable bugverifiedVerification succeededVerification succeeded
Milestone
Description
Issue Type: Bug
Behaviour
[NOTE: If you suspect that your issue is related to the Microsoft Python Language Server (python.languageServer: 'Microsoft'), please download our new language server Pylance from the VS Code marketplace to see if that fixes your issue]
Expected
For the path to my python.org install of Python 3.9 to be denoted as a global install.
Actual
Listed as "unknown" below in the output from the "Report Issue" command.
Steps to reproduce:
[NOTE: Self-contained, minimal reproducing code samples are extremely helpful and will expedite addressing your issue]
- App location is
Python interpreter path: ~\AppData\Local\Programs\Python\Python39\python.exe - Run
Python: Report Issue
Diagnostic data
- Python version (& distribution if applicable, e.g. Anaconda): Python 3.9.5
- Type of virtual environment used (e.g. conda, venv, virtualenv, etc.): unknown
- Value of the
python.languageServersetting: JediLSP
"Python" channel in the OUTPUT panel
Error 2021-06-22 16:26:42: Failed to check if file needs to be fixed [EntryNotFound (FileSystemError): Unable to read file '\brettcannon\gidgethub\.vscode\settings.json' (Error: Unable to resolve non-existing file '\brettcannon\gidgethub\.vscode\settings.json')
at _handleError (c:\Users\brcan\AppData\Local\Programs\Microsoft VS Code Insiders\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:84:155883)
at processTicksAndRejections (internal/process/task_queues.js:93:5)
at async RawFileSystem.readText (c:\Users\brcan\Repositories\microsoft\vscode-python\out\client\common\platform\fileSystem.js:90:24)
at async UpdateTestSettingService.doesFileNeedToBeFixed (c:\Users\brcan\Repositories\microsoft\vscode-python\out\client\testing\common\updateTestSettings.js:80:30)
at async c:\Users\brcan\Repositories\microsoft\vscode-python\out\client\testing\common\updateTestSettings.js:49:33
at async Promise.all (index 1)
at async UpdateTestSettingService.getFilesToBeFixed (c:\Users\brcan\Repositories\microsoft\vscode-python\out\client\testing\common\updateTestSettings.js:48:24)
at async UpdateTestSettingService.updateTestSettings (c:\Users\brcan\Repositories\microsoft\vscode-python\out\client\testing\common\updateTestSettings.js:32:32)] {
code: 'FileNotFound'
}
Extension version: 2021.7.922878407-dev
VS Code version: Code - Insiders 1.58.0-insider (d54f7e1, 2021-06-22T07:15:24.214Z)
OS version: Windows_NT x64 10.0.19043
Restricted Mode: No
System Info
| Item | Value |
|---|---|
| CPUs | Intel(R) Core(TM) i7-8665U CPU @ 1.90GHz (8 x 2112) |
| GPU Status | 2d_canvas: enabled gpu_compositing: enabled multiple_raster_threads: enabled_on oop_rasterization: enabled opengl: enabled_on rasterization: enabled skia_renderer: enabled_on video_decode: enabled vulkan: disabled_off webgl: enabled webgl2: enabled |
| Load (avg) | undefined |
| Memory (System) | 15.75GB (4.64GB free) |
| Process Argv | C:\Users\brcan\OneDrive - Microsoft\Snippets\snippets.md --crash-reporter-id 2f8216b4-0af9-4bf4-a156-6cdcff01b0ab |
| Screen Reader | no |
| VM | 0% |
A/B Experiments
vsliv695:30137379
vsins829:30139715
vsliv368cf:30146710
vsreu685:30147344
python383cf:30185419
vspor879:30202332
vspor708:30202333
vspor363:30204092
pythonvspyt639:30291487
pythontb:30258533
vspre833:30321513
vshan820:30294714
vscus158:30321503
pythonvsuse255:30319630
vscorehov:30301224
3f5j7703:30294757
vscod805cf:30301675
vscextlangct:30310089
vsccppwtct:30312693
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
area-environmentsFeatures relating to handling interpreter environmentsFeatures relating to handling interpreter environmentsbugIssue identified by VS Code Team member as probable bugIssue identified by VS Code Team member as probable bugverifiedVerification succeededVerification succeeded