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

Azure Cloud Shell Terminal successfully launches in local Windows window but fails to launch in remote WSL window #682

Closed
zombiemaker opened this issue Dec 17, 2022 · 12 comments · Fixed by #684
Labels

Comments

@zombiemaker
Copy link

  • VS Code Version: 1.74.1
  • Azure Account Extension Version: v0.11.2
  • OS Version: Windows_NT x64 10.0.22621

Steps to Reproduce:

  1. Start VS Code in Microsoft Windows

  2. Select Terminal drop down and select "Azure Cloud Shell (Bash)" (this works)

  3. Select "Open a Remote Window" (lower-left corner of VSC window)

  4. Select "Open Folder in WSL..."

  5. Select directory in WSL and select "Select Folder" (VSC connected to WSL instance)

  6. Select Terminal drop down and select "Azure Cloud Shell (Bash)"

  7. VSC Terminal panel flashes brief message ("/home/[username]/.vscode-server/bin/1ad8d514439d5077d2b0b7ee64d2ce82a9308e5a/node: bad option: --ms-enable-electron-run-as-node"

  8. VSC pops an error message box in lower-right of window with this message "The terminal process "/home/[username]/.vscode-server/extensions/ms-vscode.azure-account-0.11.2/bin/node.sh '/home/[username]/.vscode-server/bin/1ad8d514439d5077d2b0b7ee64d2ce82a9308e5a/node', '-e', 'require('/home/[username]/.vscode-server/extensions/ms-vscode.azure-account-0.11.2/dist/cloudConsoleLauncher').main()', '--ms-enable-electron-run-as-node'" failed to launch (exit code: 9)."

@alexweininger
Copy link
Member

Note: this is the same error as seen in #391

@alexweininger
Copy link
Member

alexweininger commented Dec 22, 2022

Seems like we're mistakenly adding the --ms-enable-electron-run-as-node flag when connected to a WSL instance.

@zombiemaker I'm not sure this matters, but what WSL distro are you using? Ubuntu? Also are you using WSL 2?

also, thank you for providing a detailed description

@alexweininger
Copy link
Member

I'm able to reproduce this in an Ubuntu Dev Container.

@alexweininger
Copy link
Member

@zombiemaker You can try using this development build of the extension which includes a fix for this issue. If you can verify that the fix works for you, that'd be awesome!

Download: azure-account-0.11.2.vsix.zip


Steps to install extension development build:

  1. Download the extension .VSIX: azure-account-0.11.2.vsix.zip
  2. Unzip the .zip archive
  3. From the command palette (F1 or Command/Ctrl + Shift + P), run the "Extensions: Install from VSIX..." command.
  4. Select the downloaded .VSIX file, then reload VS Code as prompted.

@pyromaniac3010
Copy link

@alexweininger I was also hit by this bug. I can confirm, that your fix works. Would be great for everyone, if this can make it in an official release soon. 😄

@alexweininger
Copy link
Member

I was also hit by this bug. I can confirm, that your fix works. Would be great for everyone, if this can make it in an official release soon. 😄

@pyromaniac3010 thank you for verifying the fix! We plan on releasing soon.

@preichelt
Copy link

preichelt commented May 4, 2023

@alexweininger something is wrong with the current 0.11.4 version. I receive an error that ends with .vscode-server/extensions/ms-vscode.azure-account-0.11.4/dist/cloudConsoleLauncher').main()'" terminated with exit code: 1. This occurs on Windows, WSL Ubuntu, and Arch Linux. The only fix I've found is uninstalling the extension, disabling extensions from auto-updating, and installing the 0.11.2 VSIX you provided here.

@alexweininger
Copy link
Member

alexweininger commented May 4, 2023

something is wrong with the current 0.11.4 version. I receive an error that ends with .vscode-server/extensions/ms-vscode.azure-account-0.11.4/dist/cloudConsoleLauncher').main()'" terminated with exit code: 1. This occurs on Windows, WSL Ubuntu, and Arch Linux. The only fix I've found is uninstalling the extension, disabling extensions from auto-updating, and installing the 0.11.2 VSIX you provided here.

@preichelt Does it work if you install version 0.11.2 of the extension from the marketplace and not from the VSIX provided above? And could you re-verify that it doesn't work on 0.11.4?

@preichelt
Copy link

@alexweininger I can confirm that 0.11.2 and 0.11.3 in the marketplace both work. Here's the error I get in Windows after going back to 0.11.4:
The terminal process "node.exe '-e', 'require('c:\\Users\\phill\\.vscode\\extensions\\ms-vscode.azure-account-0.11.4\\dist\\cloudConsoleLauncher').main()'" terminated with exit code: 1.

@alexweininger
Copy link
Member

I believe the issue you are running into is separate from the original issue posted. Could you file a new issue please?

@motorbreth
Copy link

motorbreth commented May 12, 2023

Same issue for me , version 0.11.4 error and closes terminal
The terminal process "node.exe '-e', 'require('c:\\Users\\username\\.vscode\\extensions\\ms-vscode.azure-account-0.11.4\\dist\\cloudConsoleLauncher').main()'" terminated with exit code: 1.'

Version 0.11.2 solved the issue for me

@alexweininger
Copy link
Member

Track the issue launching cloud console in #808

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants