You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
NicolasHauf opened this issue
Sep 5, 2023
· 0 comments
Labels
bashrelated to bash shell or scriptsbugSomething isn't workingpluginsrelated to plugins (for Eclipse, Intellij, VSCode, etc.)setuprelated to the setup process of devonfw-ide (setup[.bat] and devon ... setup)vscodeMicrosoft visual studio code
When installing VSCode plugins with devon the installation command sometimes fails with the error "connect ETIMEDOUT ...". Installing the plugins individually with a for loop results in the same error.
Steps to reproduce bug:
To replicate this use devon vscode setup while the plugins are not yet installed in "devonfw/plugins/vscode/".
Comments/Hints:
Command arguments can be added here. One thing to look at might be VSCode proxy settings.
The text was updated successfully, but these errors were encountered:
NicolasHauf
added
bug
Something isn't working
bash
related to bash shell or scripts
vscode
Microsoft visual studio code
plugins
related to plugins (for Eclipse, Intellij, VSCode, etc.)
setup
related to the setup process of devonfw-ide (setup[.bat] and devon ... setup)
labels
Sep 5, 2023
bashrelated to bash shell or scriptsbugSomething isn't workingpluginsrelated to plugins (for Eclipse, Intellij, VSCode, etc.)setuprelated to the setup process of devonfw-ide (setup[.bat] and devon ... setup)vscodeMicrosoft visual studio code
Description:
When installing VSCode plugins with devon the installation command sometimes fails with the error "connect ETIMEDOUT ...". Installing the plugins individually with a for loop results in the same error.
Steps to reproduce bug:
To replicate this use
devon vscode setup
while the plugins are not yet installed in "devonfw/plugins/vscode/".Comments/Hints:
Command arguments can be added here. One thing to look at might be VSCode proxy settings.
The text was updated successfully, but these errors were encountered: