vscode: Extensions not loaded the first time a remote workspace is trusted (when Azure ML ext is installed)

Issue Type: Bug

  1. Install Azure Machine Learning and Azure Machine Learning - Remote extensions
  2. Connect to remote Compute Instance using Azure Machine Learning - Remote
  3. Open a python file and try to run it

Expected: Python extension gets loaded and you can run the file using pyhton extension

Failure: Python extension is not loaded and its commands are not found

Findings

  1. Azure Machine Learning - Remote require reload image
  2. Log: [2021-07-13 13:21:27.207] [renderer9] [error] ENOENT: no such file or directory, access ‘c:/Users/sevillal/.vscode-insiders/extensions/ms-toolsai.vscode-ai-remote-0.3.0’: Error: ENOENT: no such file or directory, access ‘c:/Users/sevillal/.vscode-insiders/extensions/ms-toolsai.vscode-ai-remote-0.3.0’
  3. Reloading the window fixes the issue, python extension is loaded and its commands are available
  4. If “Azure Machine Learning - Remote” extension is installed in the remote target, and you connect with SSH - Remote, the same issue happens the first time a workspace is trusted

VS Code version: Code - Insiders 1.59.0-insider (807dfb817fef0d0c5729c1924bd4889b04fa405b, 2021-07-13T09:24:20.727Z) OS version: Windows_NT x64 10.0.19042 Restricted Mode: No Remote OS version: Linux x64 4.15.0-1098-azure

System Info
Item Value
CPUs Intel® Core™ i7-8650U 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.92GB (0.73GB free)
Process Argv –crash-reporter-id 2b925b84-77da-4382-9d6c-89a345fc2762 --crash-reporter-id 2b925b84-77da-4382-9d6c-89a345fc2762 --crash-reporter-id 2b925b84-77da-4382-9d6c-89a345fc2762 --crash-reporter-id 2b925b84-77da-4382-9d6c-89a345fc2762 --crash-reporter-id 2b925b84-77da-4382-9d6c-89a345fc2762
Screen Reader no
VM 0%
Item Value
Remote Azure ML: sevillal-dev-ci
OS Linux x64 4.15.0-1098-azure
CPUs Intel® Xeon® CPU E5-2673 v3 @ 2.40GHz (2 x 2397)
Memory (System) 6.81GB (2.40GB free)
VM 0%
Extensions (9)
Extension Author (truncated) Version
vscode-ai-remote ms- 0.3.0
remote-containers ms- 0.187.0
remote-ssh ms- 0.65.7
remote-ssh-edit ms- 0.65.7
python ms- 2021.6.944021595
vscode-pylance ms- 2021.7.2
jupyter ms- 2021.8.1025925145
vscode-ai-remote ms- 0.3.0
azure-account ms- 0.9.8
A/B Experiments
vsins829:30139715
vsliv368:30146709
vsreu685:30147344
vspor879:30202332
vspor708:30202333
vspor363:30204092
vspre833:30321513
vshan820:30294714
vscus158:30321503
vscod805cf:30301675
bridge0708:30335490

About this issue

  • Original URL
  • State: closed
  • Created 3 years ago
  • Comments: 21 (13 by maintainers)

Commits related to this issue

Most upvoted comments

@lszomoru I was testing in latest stable, sorry about that. I tested latest insider and seems to be working fine. Is there any tentative date for the next vscode release with this fix? Thanks!

@sevillal Here is what you need to do in the package.json of ms-toolsai.vscode-ai-remote:

  • "extensionKind": ["ui", "workspace"]
  • "capabilities": { "untrustedWorkspaces": { "supported": true } } (because resolvers need to execute before workspace trust is established)
  • "api": "none" (because the main extension that needs to run on the workspace side takes a dependency on this extension which runs on the ui side). this blocks the extension from exposing any API.

The current version of vscode has a bug where your -remote extension will end up executing on both the ui and the workspace side when it is being used as a resolver. I plan to fix this bug, but it will be breaking.