-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Insider update channel not working with vscode-remote #3874
Comments
This appears to be the same issue as #3800 . There must be some unknown failure during the installation and we don't log enough info. 0.24.0 is the latest now, but you'll probably hit the same issue again with 0.25.0-insiders. |
@sean-mcmanus After seeing your post, I started a remote editing session to see if v0.24.0 would be seen and then install it. I did install it, but as the dependencies were downloaded/installed the following was seen on the Output Window:
Edit: Okay, after shutting down VSC and re-launching the remote session it seems the installation completed okay:
|
I am getting the exact same message:
For version 0.25.0-insiders though. I cannot get rid of it, no matter how often I click reload, and no matter how often I do a clean shutdown + restart of VSC. I just updated VSCode and then to cpptools 0.25.0-insiders. One note to make is, that I am using remote-wsl extension to develop. What logs could I provide you for a more detailed analysis? |
hi all to suppress this I updated config file:
added string:
|
Thanks for taking care, @bobbrow |
This appears to be caused by VS Code bug #3874 (Command |
I think you meant https://github.com/microsoft/vscode/issues/78719 filed in vs code? |
@stevenguh Yeah, thanks for providing the correct link :) |
FYI, there is a workaround provided in the microsoft/vscode-remote-release#1144 (which is the same issue in my last comment) |
You mean the workaround of unzipping the .vsix ourselves to the extensions folder? Yeah, that might work (if necessary), but I think we're just going to wait for VS Code to fix their issue. |
Yes. I tried the workaround, and it works with vs code remote ssh for me. I think it make sense to wait for VS Code to fix their bug. At least there is a workaround for people eager to try. |
When to update this extension for today while running VS Code 1.39.1 and now see it on the host machine, Windows 10 Updating C/C++ dependencies... Downloading package 'C/C++ language components (Windows)' (5692 KB) Failed. Retrying...(5692 KB) Done! Installing package 'C/C++ language components (Windows)' If you work in an offline environment or repeatedly see this error, try downloading a version of the extension with all the dependencies pre-included from https://github.com/Microsoft/vscode-cpptools/releases, then use the "Install from VSIX" command in VS Code to install it. |
@bobbrow @michelleangela @Colengms VS Code fixed their issue but we're still failing to install remotely (I tried WSL) with error "Failed to find VS Code script". |
The Insider channel should work with vscode-remote with https://github.com/microsoft/vscode-cpptools/releases/tag/0.26.3 (after we have our next Insiders available). |
@hoopoepg Your solution worked for me! Thank you! |
Hello,
VSCode recently updated to 1.36 and the Remote-SSH extension was recently updated as I was waiting for this action item to be addressed, Handle Proxy Issues on Remote
I am able to install extension on the remote session which the main extension is this one, vscode-cpptools. This extension was installed/updated to 0.23.1. Now, I keep getting the notification of "The C/C++ Extension has been updated to version 0.24.0-insiders3. Please reload the window for the changes to take effect"
After I press the "Reload" button and VSCode restarts the same message reappears after a few minutes. I had reloaded and restarted the remote session a number of times, but I still keep getting this notification. I am not sure this is problem with this extension or the remote extension.
For now, I changed the configuration option C_Cpp:Update Channdel to "default" instead of "Insiders", though I would like to use the Insiders channel.
Mark
The text was updated successfully, but these errors were encountered: