Remote tunnel error when trying to keep the tunnel active
I’m trying to start remote tunnel with:
Running VS Code via WSL2 no longer auto-focuses the Terminal tab in panel
I don’t know what changed, but after running code . to start a Remote Development session from WSL2 Ubuntu (normally having already entered my virtualenv shell via pipenv) the Panel UI with multiple tabs (Output, Ports, Terminal, etc.) is not longer auto-focused to the Terminal “tab” and instead usually drops me into the Problems or lang. server tab. Sometimes the Panel doesn’t come up at all and I have to select Terminal from the top options menu.
White screen (1-2 sec) when Switching to VSCode
When switching between apps and switching back to VSCode, the screen goes white for 1-2 sec. I’ve noticed that the longer VSCode has been in the background the longer the white screen (1-2 sec is max tho).
The problem of being unable to navigate functions encountered while using VS Code
While using VS Code, I encountered an issue where I couldn’t navigate functions within the WSL: Ubuntu environment.
extensions exist on remote box , but are shown as missing; extensions.json is an empty list
I have a VirtualBox instance (Debian12) under Windows which serves as an Ansible controller.