Greetings!
Note to admins:
I'm really not sure where to put this - I would have suspected "Troubleshooting" - but that seems to be limited to actual Raspberry Pi issues itself. So, not knowing where else to put it, I put it here. If you move this discussion to a more relevant forum, please delete this apology.
Items within brackets are footnotes.
Configuration:
Several years ago, (back in 2020), I was working on a GoPiGo robot project using Visual Studio Code, remote development on the robot itself running Buster. Everything worked wonderfully, development was proceeding, and all was well in the world. At that time, the current version of Visual Studio Code was 1.6.n - it is now 1.9.1
Then. . . .
The Coronavirus, multiple family issues as a result of it, (including a long and grueling rehab), knee surgery, (etc.), conspired to keep me away from this project until now. (July, 2024)
I restarted the project with a fresh install of both Visual Studio Code[1] and Raspberry Pi O/S, (configured for the GoPiGp robot), and attempted to launch VS Code and begin anew.
Expected Results:
An extensive search online returned few results, the only relevant result being one that mentioned that after VS Code version 1.8.9 (or so), special configuration changes were made and to back-rev to 1.8.5. When I back rev'd to 1.8.5, all the necessary extensions appeared to be unavailable. Upgrading to 1.8.6 or 1.8.7 did not help.
Additional context:
It should be noted that the .vscode-server directory and files are installed in the user's (pi) home directory as expected. No log files were found there.
Attempting to open the remote server continues until I manually stop it, with no terminal errors reported within VS Code.
/var/log: syslog, messages, kernlog, and userlog contained nothing about attempts to connect or permission errors.
Any help would be gratefully appreciated.
======== Footnotes ========
Note to admins:
I'm really not sure where to put this - I would have suspected "Troubleshooting" - but that seems to be limited to actual Raspberry Pi issues itself. So, not knowing where else to put it, I put it here. If you move this discussion to a more relevant forum, please delete this apology.
Items within brackets are footnotes.
Configuration:
- A fresh install of VS Studio Code 1.9.1[1] on Windows 10, current as of this instant date, and the "Remote Access" extension has been installed.
- Raspberry Pi O/S Buster. This is a version especially configured for the GoPiGo robot. It is also fully updated as of this instant date as well.
Note that Buster is a hard requirement and cannot be changed.
Also note that prior to this incident, this same version of Buster worked with Visual Studio Code.
Several years ago, (back in 2020), I was working on a GoPiGo robot project using Visual Studio Code, remote development on the robot itself running Buster. Everything worked wonderfully, development was proceeding, and all was well in the world. At that time, the current version of Visual Studio Code was 1.6.n - it is now 1.9.1
Then. . . .
The Coronavirus, multiple family issues as a result of it, (including a long and grueling rehab), knee surgery, (etc.), conspired to keep me away from this project until now. (July, 2024)
I restarted the project with a fresh install of both Visual Studio Code[1] and Raspberry Pi O/S, (configured for the GoPiGp robot), and attempted to launch VS Code and begin anew.
Expected Results:
- VS Code would do whatever updates it required.
- It would re-install the VS Code server "shim" on the robot as before.
- I would clone the existing repository to the new installation and continue from there as before
- VS Code can successfully connect to the Raspberry Pi. (Likewise, so can PUTTY, etc.)
- VS Code starts to download the server. It asks for the platform type, (Linux), and the password.
- It proceeds for about 30 seconds to a minute, then goes back to the second step repeatedly, seemingly stuck in a loop.
An extensive search online returned few results, the only relevant result being one that mentioned that after VS Code version 1.8.9 (or so), special configuration changes were made and to back-rev to 1.8.5. When I back rev'd to 1.8.5, all the necessary extensions appeared to be unavailable. Upgrading to 1.8.6 or 1.8.7 did not help.
Additional context:
It should be noted that the .vscode-server directory and files are installed in the user's (pi) home directory as expected. No log files were found there.
Attempting to open the remote server continues until I manually stop it, with no terminal errors reported within VS Code.
/var/log: syslog, messages, kernlog, and userlog contained nothing about attempts to connect or permission errors.
Any help would be gratefully appreciated.
======== Footnotes ========
- I also tried this with the original installation that automatically updated to 1.9.1 and it was no different. I decided to backup the original VS Code context, delete it completely, and then create a fresh install without all the extensions installed to eliminate possible conflicts.
Statistics: Posted by jharris1993 — Wed Jul 10, 2024 4:31 pm