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
I encountered an issue while trying to set up the extension manager with my local VSCode WSL setup. Here are the details of the problem:
I successfully added a private registry to the extension manager, and it worked fine for a colleague. To prevent a bug related to the Artifactory repository used, I added the following configuration in the settings:
However, when I attempted to access the page where the extensions should be listed, it kept loading indefinitely. Additionally, I noticed an error in the "Developer Tools" of VSCode, although I'm not entirely certain if it's related to this issue. The error is already described here: #87
In an attempt to resolve the issue, I downgraded my VSCode to version 1.78.2, which is the same version installed on an Ubuntu 22.04 VM. Interestingly, the setup worked flawlessly in the Ubuntu VM with the same configuration.
Based on this experience, it appears that the issue might be related to the electron/node.js version bundled with VSCode. Currently, my VSCode instance (1.82.1) is running Node.js version 18.15.0, whereas in the 1.78.2 release, it was running Node.js version 16.17.1.
Steps to Reproduce:
Set up a local VSCode WSL environment.
Add a private registry with the following settings:
Attempt to access the extensions page within VSCode. Expected Behavior:
The extensions page should load and display the available extensions from the private registry without any issues.
Actual Behavior:
The extensions page keeps loading indefinitely, and there may be errors in the "Developer Tools" console.
Environment:
Operating System: Windows 10
VSCode Version: 1.82.1
Behind company proxy.
Repository is located inside the company network (no_proxy must be respected).
Additional Information:
The issue seems to be specific to the electron/node.js version bundled with VSCode.
Downgrading to VSCode version 1.78.2 on an Ubuntu VM with the same setup works as expected.
This issue is affecting my workflow, and I would appreciate any assistance in resolving it. However, the root cause of the issue seems to be that the extension is not able to process the system no_proxy properly due to outdated package-versions.
Thank you!
The text was updated successfully, but these errors were encountered:
Issue Description:
I encountered an issue while trying to set up the extension manager with my local VSCode WSL setup. Here are the details of the problem:
I successfully added a private registry to the extension manager, and it worked fine for a colleague. To prevent a bug related to the Artifactory repository used, I added the following configuration in the settings:
However, when I attempted to access the page where the extensions should be listed, it kept loading indefinitely. Additionally, I noticed an error in the "Developer Tools" of VSCode, although I'm not entirely certain if it's related to this issue. The error is already described here: #87
In an attempt to resolve the issue, I downgraded my VSCode to version 1.78.2, which is the same version installed on an Ubuntu 22.04 VM. Interestingly, the setup worked flawlessly in the Ubuntu VM with the same configuration.
Based on this experience, it appears that the issue might be related to the electron/node.js version bundled with VSCode. Currently, my VSCode instance (1.82.1) is running Node.js version 18.15.0, whereas in the 1.78.2 release, it was running Node.js version 16.17.1.
Steps to Reproduce:
Set up a local VSCode WSL environment.
Add a private registry with the following settings:
Attempt to access the extensions page within VSCode.
Expected Behavior:
The extensions page should load and display the available extensions from the private registry without any issues.
Actual Behavior:
The extensions page keeps loading indefinitely, and there may be errors in the "Developer Tools" console.
Environment:
Operating System: Windows 10
VSCode Version: 1.82.1
Behind company proxy.
Repository is located inside the company network (no_proxy must be respected).
Additional Information:
The issue seems to be specific to the electron/node.js version bundled with VSCode.
Downgrading to VSCode version 1.78.2 on an Ubuntu VM with the same setup works as expected.
This issue is affecting my workflow, and I would appreciate any assistance in resolving it.
However, the root cause of the issue seems to be that the extension is not able to process the system no_proxy properly due to outdated package-versions.
Thank you!
The text was updated successfully, but these errors were encountered: