how to delete an existing jupyter server in vscode - visual-studio-code

i'm using remote jupyter server in vscode.i added remote server as the guide says.
But what annoying me now is that i created too many server url but don't know how to delete one.
Does anyone know how to deal with it? Or i should uninstall and reinstall totally.

You can run the command (CMD+SHIFT+P on MAC):
>Jupyter: Clear Jupyter server list

Related

code tunnel -h doesn't list options and doesn't open a tunnel to WSL

I'm following the guide
and I am noticing that code tunnel -h in a ubuntu terminal window just launches the code UI.
Using the command palette to get the URI results in a tunnel to my Windows version of VSCode rather than the WSL:ubuntu (which is the one I care about)
How do I fix this?
It appears that, for now, you need to manually install the CLI in WSL in order for it to work. The downloads can be found here. Since you are on Windows, I would recommend the x64 CLI download. When you extract the tar.gz file, you will get a file named code. I would recommend moving it to your home directory for ease. To open the tunnel, run ./code tunnel (from wherever you put the code file) to force the new CLI. If you use code tunnel it will still use the Windows version.
Source: https://github.com/microsoft/vscode/issues/171196

is there a way to work offline with vscode remote ssh to save cost?

I am using vscode ssh remote plugin https://code.visualstudio.com/docs/remote/ssh
to connect to gcp sandbox vm. gcp sandbox vm has an hourly cost if kept turned on.
most of the time I am reading or changing the code and I am not running any command in the VM's terminal. So, if I had the code offline, I would not need to keep the VM running and pay for each second of it.
Is there a way I can do this?
When using VSCode over SSH, you are running a VSCode server on the remote host which is used to read the files.
If you want to be able to open files locally, you will need to download them.
If you already have the files opened, you can disconnect from the VM and keep looking at them.
Another option to consider is mounting whatever file store you're using locally as a FUSE file system. Here is an example for git: https://github.com/presslabs/gitfs

Failed to connect to the remote extension host server (Error: Missing proxy instance MainThreadDebugService)

Hey stackoverflow community i have an issue with vscode connecting to wsl2 with the following error [picture bellow] message i already searched for hours and couldnt find a solution.
reinstalled both with a clean updated version without any success
Edit 1:Tried to unmount and remount folders also tried opening with high privilege's from cmd 'wsl code .' moreover i completely deleted wsl and vscode with all the extensions but still am getting the same error, i was able to reproduce more readable error, when opening a project it prompts with
unable to resolve resource vscode-re...://%ubuntu-22.04/file_path
Edit 2: opening WSL, 'New WSL window using distro' works fine but i cant open any directory, without it producing the error in Edit 1
I got the same issue. I use Windows and I open the folder in vscode in this way:
shift+right-click the folder -> open linux shell -> type in "code ."
when vscode opens, the error does not exist.
For me this was due to the secondary sidebar being visible.
After disabling it via View -> Appearance -> Secondary Side Bar, WSL2 starts up fine again.
I got the same.
If your project is on another drive mount it and
run vscode as administrator.
I had this issue and needed to run..
$ code
Updating VS Code Server to version 97dec172d3256f8ca4bfb2143f3f76b503ca0534
Removing previous installation...
Installing VS Code Server for x64 (97dec172d3256f8ca4bfb2143f3f76b503ca0534)
Downloading: 100%
Unpacking: 100%
Unpacked 2389 files and folders to /home/dmitri/.vscode-server/bin/97dec172d3256f8ca4bfb2143f3f76b503ca0534.
in WSL2 to update the WSL2 server. Then uninstalling and reinstalling the WSL extension from VSCode did the trick.
I am the same.
I also reinstalled VSCode and Docker, but nothing changed.
In the "Remote - Containers" tutorial, I was able to connect without any problems.
It doesn't work with my code.

cannot connect to the remote wsl on vs code (Error: [UriError]: cannot call joinPath on URI without path)

i'm trying to use wsl on vs code. it worked well until it unexpectedly stopped working.
Any ideas on how can i fix this? I tried to uninstall and reinstall vs code as well as stopping the remote server but it did not work either. I'm still stuck on the workspace page without the possibility to do anything.
Thanks in advance.
Uninstalling doesn't affect the vscode server files in your home directory. Removing said files will cause a fresh install of said server and remote container files. So,
rm -r ~/.vscode*
code <wherever_you_like>

Fatal Error. application server could not be contacted

I would like to install PostgreSQL on windows 7. Howver I faced one problem when I am going to launch pgAdmin 4. It shows that "Fatal Error. application server could not be contacted." I tried run as Administrator, deleted file pgAdmin in AppData. Deleted python and in my path. Added PostgreAQL in my path. However due to some reason it shows the above proble. I need your help. Thank you in advance
Here is the solution that worked for me on windows 10:
Delete the pgAdmin folder from AppData C:\Users\%USERNAME%\AppData\Roaming\pgAdmin (Note: AppData is a hidden folder),
Search for "Services" with windows search, scroll down to postgres and click on "stop",
Run pgAdmin as Administrator.
Unistall existing postgresql on your computer.This should uninstall the entire applications associated with postgresql including pgadmin4. Go to your start menu and type in "pgadmin4" to show if you still have associated file.If you see any,trace the location and delete it.
You can now re-install a fresh copy of POSTGRESQL from Enterprisedb which will automatically install pgadmin4 for you. The new installation will prompt you to enter new password. Use a password you can remember since you will always need it to access the database.
I uninstalled my python IDLE and then installed the latest python IDLE. When installed it will give you an option if you should allow all programs including python to have full access to the AppData PATH choose yes and the fatal error will disappear