Problem with PROS VSCode Extension

[01101101]

Windows 10 device, no python installed, no vscode installed, no pros cli installed.

1. Installed VSCode for the main user:
   
2. Installed PROS extension:
   
   
3. Pressed Install now on ‘CLI not working’ pop-up!
   
4. ‘Finished installing VEXcom’ appears, ‘preparing to install PROS’ disappears
   
5. Pressed create project in PROS extension
   
   
   
   
   
   
   
   
6. As soon as I press enter, before being able to input the pros kernel version I get:
   
   
   
7. Restarting VSCode I get this again:
   
8. Attempting to use the pros-conductor command in the integrated terminal predictably gives me this:
   
   

So the pros cli which was installed by the pros VScode extension does not work properly due some python related issue?

I will now try installing the pros cli directly from the latest github release Release 3.4.3 - Squashing the Big Bug 🐛🐛🐛 · purduesigbots/pros-cli · GitHub :

1. Created a new directory in Program Files:
   
2. Extracted archive to this new location:
   
3. Added new PATH entry for main user:
   
   
4. Running pros conductor in command prompt gives this:
   
   
5. Looks like the PROS toolchain needs to be installed! The only place I could find somewhere to install the windows toolchain is this old 3.3.3 installer sitting in downloads:
   
   Should I try running this and selecting ‘toolchain on PATH’? Even if this does end up working, the main issue is that the VSCode extension doesn’t appear to be functional!

This looks to be the same issue but is unresolved? Could anyone recreate this on their device? Any help would be greatly appreciated.

PROS CLI issues

Running the pros command in cmd gives me the following error: Python path configuration: PYTHONHOME = (not set) PYTHONPATH = (not set) program name = 'C:\Program Files\PROS\cli\pros.exe' isolated = 0 environment = 0 user site = 1 import site = 0 sys._base_executable = 'C:\\Program Files\\PROS\\cli\\pros.exe' sys.base_prefix = '' sys.base_exec_prefix = '' sys.platlibdir = 'lib' sys.executable = 'C:\\Program Files\\PROS\\cli\\pros.exe' sys.prefix = '' sys.exec_prefix =…

[BennyBoy]

I will attempt to recreate this later today.
In the meantime, we can fix your non-vscode installation so you have something working. The CLI installation you did is fine. For toolchain installation, go to Release PROS Toolchain 10.3-2021.10 · purduesigbots/toolchain · GitHub and download the zip called pros-toolchain-windows-formatted.zip. Extract this, and then add the bin folder inside to PATH. That should fix your toolchain problem. I’ll get back to you about your vscode problem, I haven’t seen this issue before.

[01101101]

Thanks for the prompt reply, having extracted said archive to a location in program files and having added the path of the bin directory to the PATH variable I still reciveve this error on running the pros conductor new-project command from a fresh command line:

I can verify the toolchain is indeed installed by running the ‘make’ command in the command prompt:

This error is probably a basic mistake on my part but I can’t seem to find the cause of the problem so any advice would be appreciated! Thanks once again for looking into the more pressing vscode extension issue, I hope you can manage to recreate it or otherwise find where I’ve made a mistake!

[01101101]

Thanks again Benny for the help so far. If anyone else reading this has a working pros installation and is willing to give me a quick explanation of how you got it to work it would be greatly appreciated! Or if anyone is willing to do a fresh pros installation and run me through their steps to get it working that would be awesome too. Cheers.

[BennyBoy]

Try also creating a new environment variable called PROS_TOOLCHAIN that points to the toolchain’s root folder (the one that contains usr, bin, tmp). Also make sure that you restarted the terminal after adding the environment variable.

I was unable to reproduce your initial VSCode issue. could you send me some more specifics (VSCode version, windows version, etc. Another thing you could try is transporting the working cli to be in the correct place for VSCode installation. Just move the working cli contents to C:\Users\YOURUSERNAME\AppData\Roaming\Code\User\globalStorage\sigbots.pros\install\pros-cli-windows. While you are there, can you see if there is another folder called pros-toolchain-windows? The installer is not giving you any hassle about the toolchain not working or being out of date, so maybe that toolchain will work as expected (?).

[01101101]

Thanks for giving this your time.

At the minute I’ve replaced C:\Users\YOURUSERNAME\AppData\Roaming\Code\User\globalStorage\sigbots.pros\install\pros-cli-windows with pros_cli-3.4.3-win-64bit which I cloned straight from the sigbots github. It also looks like the toolchain has also been installed by the extension (directory structure looks normal at first glance) Upon opening VScode I first got ‘preparing to install PROS’ then got ‘PROS toolchain and CLI are working’ (or words to that effect).

When I used the create project button in the extension it took a good long while before finally completing successfully! It appears that the PROS extension now works after porting the CLI directory. That also suggests the toolchain which it installed is also working properly and is the right version.

I used a tool to find any differences in the directory structures and found that the following files where missing in the directory installed by the PROS extension:

Thanks so much for looking into this, I don’t know whether you want to pursue this further but in case you do, i’ll list some specs/versions:

OS:

VSCode (installed yesterday):

[01101101]

Also for future reference if anyone looks into to this, whenever I now start VSCode it pops up with ‘preparing to install PROS’ for about 30 seconds. The extension seems to work fine other than that though but if I’m not connected to the internet it stays there indefinitely with no way to close it so it’s quite annoying, especially because it covers the bottom of the integrated terminal on my small display so you can’t see what your typing!

[BennyBoy]

This is the auto updater running. You can disable it by navigating to your user settings → extensions → PROS.