Platformio-vscode-ide: The latest VSCode 1.37 seems to break PlatformIO

[ssilverman]

I'm still diving into this, but when I just upgraded to VSCode v1.37.0, it broke something about platformio paths:

> Executing task: platformio run <

The terminal shell path "platformio" does not exist

[ssilverman]

I tried a reinstall of the PlatformIO extension, but that doesn't work either.

[ssilverman]

I just tried deleting my ~/.platformio directory, and after it rebuilt itself, I still get the same error.

[valeros]

Hi @ssilverman! What is your OS? Can't reproduce the issue on a Windows machine.

[ssilverman]

I also just tried setting this in my custom settings, and this didn't work either:

"platformio-ide.customPATH": "/Users/shawn/.platformio/penv/bin:/Users/shawn/.platformio/penv"

My OS is OSX 10.14.6.

[ssilverman]

I verified I don't have other platformio's in my path, and also verified that there are none installed via brew or pip.

Next up: A complete re-install of VSCode and PlatformIO.

[ssilverman]

Ok, I just completely deleted the app plus ~/.platformio then did a reinstall. No dice :(

[ssilverman]

New detail: I can open a VSCode terminal and run commands manually from there, that works fine. It's when running anything PlatformIO from the "Run Task..." list.

[valeros]

Thanks for the info, it seems like v1.37 breaks the extension on Unix based OS. As a workaround, you can globally install PlatformIO until we fix it.

[pczekalski]

Same here. Ubuntu 19.04, VS 1.3.7, PIO 4.0.0.
Could you give some details on what "you can globally install PlatformIO" means? Installing via pip nor pip3 does not help, either.

[valeros]

Forget to mention that you also need to disable the Use Builtin PIOCore option in
Settings->Extensions->PlatformIO IDE Configuration

[pczekalski]

Thx - it works this way (at least compiles).

[SigmundurJohansen]

Is there a fix comming?

[sstaub]

I have the same problem with macOS Catalina beta, on Mojave VSCode 1.37 works without a problem.

[tuxBurner]

Have the same issue https://github.com/MarlinFirmware/Marlin/issues/14887#issuecomment-519994880

[Tatukis]

Same here. Ubuntu 19.04, VS 1.3.7, PIO 4.0.0.
Could you give some details on what "you can globally install PlatformIO" means? Installing via pip nor pip3 does not help, either.

I just use the SuperQuick install in the plataformio page (python -c "$(curl -fsSL https://raw.githubusercontent.com/platformio/platformio/develop/scripts/get-platformio.py)")
EDIT: Probably with sudo.

[ryanburketllc]

Uninstalling and reinstalling PlatformIO from the vscode extensions menu didn't do anything for me, but following Tatukis' advice, the SuperQuick installer for mac running from within the vscode terminal resolved it for me. Made for a frustrating morning though... https://docs.platformio.org/en/latest/installation.html#super-quick-mac-linux

[joaodematejr]

+1 Mac Os Mojave 10.14.6

[giotherobot]

Confirmed also on Linux Debian Buster.
Confirmed also that the problem is in the Tasks, using platformio thru cli still works with the integrated version, no need to install system-wide.

[pfeerick]

Perils of updating as soon as it's released... Should know better with Micro$haft... always wait for the second revision! 😆 Can confirm it isn't causing issues on my Windows 10, not sure about Linux yet, not updating to 1.37 on my daily until this is fixed!

Confirmed on an otherwise pristine Ubuntu 18.04 VM... simply updating to VSCode 1.37 broke most commands from the extension that run platformio... except for launching PIO Home or doing an upgrade check. Allowing path modification had not effect whatsoever, and there isn't anything of interest in the debug log - no errors or such. Launching a new VSCode terminal and running platformio works though! 😱

[zerog2k]

on mac, after rolling back to 1.36.1 it's working again
(https://code.visualstudio.com/updates/v1_36)

@ivankravets ^

[phhoef]

Same here for VSCode.
It seems, that the build/upload task won't open the PlatformIO Shell properly.
When clicking in the bottom bar to open a shell window and manually executing platformio run --target upload it is working fine. So I guess the installation is not completely broken ...

[kbhuinfo]

Same here. Ubuntu 19.04, VS 1.3.7, PIO 4.0.0.
Could you give some details on what "you can globally install PlatformIO" means? Installing via pip nor pip3 does not help, either.

I just use the SuperQuick install in the plataformio page (python -c "$(curl -fsSL https://raw.githubusercontent.com/platformio/platformio/develop/scripts/get-platformio.py)")
EDIT: Probably with sudo.

That is the only method, that worked for me (kubuntu 19.04 / vsc 1.37 / Pio4.0.0)

[ivankravets]

This is a bug of VSCode. It's 2nd time when a new release of VSCode breaks Tasks API. The current workaround is to downgrade VSCode to 1.36.

@alexr00, @Tyriar, @dbaeumer could you explain how to fix it now? We use ProcessExecution API, see https://github.com/platformio/platformio-vscode-ide/blob/develop/src/tasks.js#L68

[ivankravets]

Please update to https://github.com/platformio/platformio-vscode-ide/releases/tag/v1.8.2

We switched temporarily to VSCode ShellExecution API.

[taburet]

Thanks for the super quick fix!

[Tyriar]

@alexr00 might be a candidate for recovery build for ProcessExecution?

[SigmundurJohansen]

@ivankravets updating to 1.8.2 did not fix it for me

[ivankravets]

@SigmundurJohansen what is your OS and default shell?

[SigmundurJohansen]

@ivankravets
Ubuntu 18.04.2 LTS
bin/bash

[ivankravets]

I don’t have more ideas for workarounds. Let’s wait for the official tips from VSCode team.

We could actually try to play with system shells and detect it automatically. However, this is “dirty way”.

[sstaub]

Now it works with macOS Catalina beta.

[giotherobot]

Works fine on Debian Buster.
Thanks for quick fix!

[pfeerick]

v1.82 works fine on a KUbuntu VM and my daily Manjaro Arch with VSCode 1.37. Thanks! :smile:

[alexr00]

@ivankravets and @Tyriar thank you for tagging me. Yes, this is absolutely a candidate for the recovery build. Corresponding VS Code issue: https://github.com/microsoft/vscode/issues/78898

[ivankravets]

@alexr00 thanks for the quick fix! What is the right API in our case? Should we use ProcessExecution or ShellExecution if we call platformio.exe binary? It seems like it should be ProcessExecution.

[alexr00]

Since you are calling platformio.exe ProcessExecution is a better fit.

[alexr00]

The fix will go out in 1.37.1 and will also be available in the next insiders build.

[ivankravets]

@alexr00 Thanks! We will revert back to ProcessExecution when 1.37.1 is out.

[ivankravets]

Do you have any ETA for 1.37.1?

[Tyriar]

@ivankravets likely mid-late this week

[ivankravets]

@SigmundurJohansen does it work with the latest VSCode 1.37.1? It's already released.

[pczekalski]

No, it does not. Fails in installing core.

On Fri, 16 Aug 2019, 23:47 Ivan Kravets, [e-mail] wrote:

@SigmundurJohansen https://github.com/SigmundurJohansen does it work
with the latest VSCode 1.37.1? It's already released.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/platformio/platformio-vscode-ide/issues/957?email_source=notifications&email_token=AFVAVRXR3F2QMSTTMD4UNFLQE4N77A5CNFSM4IKSJHW2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD4PY5AI#issuecomment-522161793,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFVAVRQOW3VCW6LCZFBBICTQE4N77ANCNFSM4IKSJHWQ
.

[pfeerick]

@pczekalski That sounds to be completely different issue as this one is only related to ability to run commands via the PlatformIO extension (refer to the first post in this thread), not installation (or perhaps reinstallation in your case?) of PlatformIO via the extension.

On VSCode 1.37.0, with v1.81 of the extension (pre-workaround) I can confirm it was broken on KUbuntu. I then updated to VSCode 1.37.1 and the issue is now gone. Sweet!

[ivankravets]

@pczekalski please file a new issue here https://github.com/platformio/platformio-vscode-ide/issues with all details.