How to package VS Code Extension behind proxy - visual-studio-code

I have created a VS Code extension that I want to distribute within my organization. My system runs behind a corporate proxy threfore when I try to create a publisher using the command vsce create-publisher (publisher name) I get following error:
ERROR tunneling socket could not be established, statusCode=407
It does not accept --proxy-server option that VS Code supports while installing extensions.

proxies are not supported by VSCE for now. It can published outside corporate networks only. This issue is open for last three years on github.
Please find this issue link.
https://github.com/Microsoft/vscode-vsce/issues/157

Related

Getting VS code server to run on Sagemaker Studio

I am currently in the process of exploring the possible use of VS Code Server on Sagemaker Studio. Of course, if you sign up through Code Server preview, I was able to set and start it up. However, when I tried to serve it locally, I encountered a blank page after modifying the /default/proxy/XXX part of the url like how we access tensorboard.
Just wondering on whether are there any tinkerers out there that managed to get it working? (and yes, I understand that somebody managed to get it running https://coder.com/docs/code-server/latest/CONTRIBUTING. but wondering whether anybody managed to use the native installation to work properly? Any possible steps that i may be missing?
Check out the blog post here for hosting code-server on SageMaker Studio - https://aws.amazon.com/blogs/machine-learning/host-code-server-on-amazon-sagemaker/
And associated git repo here - https://github.com/aws-samples/amazon-sagemaker-codeserver

VS Code Remote Development Errors

I am connected to my company's VPN on my Windows 10 desktop and uses VS Code for my development. I wanted to use VS Code Remote Development so that I can connect to my remote company development server and autosave my files directly on the server. I have installed VS Code Remote Development package and this is my SSH config.
Host my.company.server
HostName 10.XXX.XXX.XX6
User root
IdentityFile C:\Users\My_User\Documents\Company\company_key.pem
However, when connect VS Code to the remote server, VS Code shows that I am connected but I am getting the errors below and cannot view the remote directory.
Unable to write to Folder Settings because no resource is provided.
Could not fetch remote environment.
Failed to connect to the remote extension host server
(Error: Websocket close with status code 1006)
I tried connecting to the remote server using WinSCP and that works fine. I also used PowerShell to login using the below command and that works fine too.
ssh -i C:\Users\My_User\Documents\Company\company_key.pem root#10.XXX.XXX.XX6
What am I doing wrong here? Any VS Code gurus can assist me with this issue? Thanks.
VSCode was attempting to download and install several components on that remote machine, which probably was blocked by the machine administrators in your company (as downloading from an external resource is commonly seen as a security risk on an internal machine).
You should carefully review the information security policies of the company before making any violation. And then discuss with your manager to see if VSCode Remote should be used or not.

Setting Corporate network proxy in Visual Studio Code?

I'm trying to use the Visual Studio Code IDE for Salesforce development. The IDE works fine in my personal network, where I can retrieve and upload the metadata file without any issue. When I connect to my office network I'm not able to do the same.The Salesforce CLI shows the following error while retrieving the metadata -
"error: connect etimedout 85.224.145.196:443"
Later I got to know that I will have to set up the network proxy in VS Code. I have gone through the following links and tried to add the proxy to the
VS code. Unfortunately, nothing worked for me -
Getting connect ETIMEDOUT when trying to install a VSCODE extension
http://www.niranjankala.in/post/How-to-setup-Proxy-settings-in-Visual-Studio-Code
I used to set the proxy in eclipse in this way-
Preference >> Network connection >> Proxy entries -
Schema: "HTTP" ,Host:Proxy URL of the company,Port:8080,Auth:"No" AND Proxy Bypass - Host:127.0.0.1, Provider:Manual
If somebody faced this before request you to share the way to resolve this issue. Thanks in advance!

Cannot update repository Windows Azure

I'm trying Windows Azure now.
I have been following instruction from
https://www.windowsazure.com/en-us/develop/java/java-home/download-the-windows-azure-sdk-for-java/
I'm running on eclipse helios, but when i try to install new software and enter url repository :http://dl.windowsazure.com/eclipse
Eclipse always timeout,
message on message box like bellow :
Unable to connect to repository http://dl.windowsazure.com/eclipse/content.xml
Unable to connect to repository http://dl.windowsazure.com/eclipse/content.xml
Connection timed out: connect
How to solve this, i very need it to deploy my first app on Windows Azure platform
Help me to solve this, please
Now i try to runnning azure project on Cloud Azure, but why when i try to upload cspkg file and cscfg file, the process always timeout, whereas connection is running normally when i look on ping -t
this is message when i try upload on azure hosting service :
Uploading the selected package has failed, please verify your network connection and try again.
How to solve this issue ?
it's very strange error. >-<
I think there is some problem with your network connection as I have just tested the same download location and it does work perfectly fine as below:
As you can see below I am using http://dl.windowsazure.com/eclipse URL to download the Java specific Azure components:
After that once I select "Next", the following two components are listed to be installed in my machine:
Microsoft JDBC Drive 3.0 for SQL Server (This will work with SQL Azure)
Windows Azure Plugin for Eclipse with Java
I am sure that the problem is specific to your network connection so please have it corrected.
Yes, it's foolish of me, i forget to shutting down my proxy server on My compute.After i disable it,everything gonna be alright :D
Thanks
surely I haven't meet this situation before , but just for your additional information..
Have you follow this step on installing azure #eclipse? like .net version must be >= 3.5
here are some source link for your help http://www.windowsazure4e.org/download/
I haven’t worked with Windows Azure Java SDK. But the error message is complaining the file C:\Users\workspace\AzureFirst\emulatorTools\ResetEmulator.cmd cannot be found. It would be better if you can check whether the file exists. In addition, the call stack points out you’re using Windows Azure SDK 1.4. Please try to upgrade it to 1.6 to see whether it works fine. You can find SDK 1.6 on http://www.microsoft.com/en-us/download/details.aspx?id=28045. Please install WindowsAzureEmulator and WindowsAzureSDK. The WindowsAzureLibsForNet is not needed if you don’t want to use .NET.
Best Regards,
Ming Xu.

Nuget Server returning 403's and 404's

I'm trying to host nuget on my Amazon EC2 VPS, and I'm having issues.
I've followed the instructions here ( Hosting your own NuGet Feeds )
I've read this thread ( NuGet: remote server returned an Error(403) Forbidden ) along the same lines.
I'm not running TFS
It "could" be a proxy issue, but I'm not entirely sure how to check.
My NuGet feed is located at http://nuget.infinitas.ws. You'll notice that both http://nuget.infinitas.ws/nuget/Packages and http://nuget.infinitas.ws/Packages are throwing errors.
Any help with this will be greatly appreciated.
You are probably running the NuGet.Server in a Web Site-project. Try to run it via an ASP.NET Web Application instead (in Visual Studio you can create one via File -> New -> Project -> ASP.NET Web Application)
Have you tried the latest version (1.5)?
The release notes include some changes related to proxy authentication:
Support for Proxies that require authentication
When using NuGet behind a proxy that requires authentication, NuGet will now prompt for proxy credentials. Entering credentials allows NuGet to connect to the remote repository.
I realize I'm a little late to the party but I've just spent a frustrating couple of hours with the same problem.
I found that switching the Application Pool from "Classic" to "Integrated" fixed the problem