Closed wtakuo closed 3 months ago
@wtakuo Thanks for taking the time to report this bug in this very detailed issue and providing a PR to fix it ASAP. I'm sorry that you had this bug, it should have definitely get caught during testing. I'll include your fix in the next patch which will be released today.
What are the steps to reproduce this issue?
What happens?
What were you expecting to happen?
For example, if we select port ESP32 version 1.23.0.post1, the following error dialog will appear. Similar results are obtained for the other combinations.
Any logs, error output, etc?
(To get extension logs see Terminal > Output > Extension Host and copy output concerning pico-w-go or micropico) (If it’s long, please paste to https://gist.github.com and insert the link here)
Any other comments?
Perhaps the cause is that in the following code (
activator.mts
, lines 1121-1130), the value ofObject.keys( availableStubVersions).length
is always 1 because the type ofavailableStubVersions
is{[key: string]: string[]}
.This causes
versions
to be just a list of version number strings, and in the following code (activator.mts
, line 1152),versionParts
is set to a different value than expected.The above code can be changed as follows to achieve the expected behavior.
Which version of MicroPico are you using?
3.7.8
Support info
Copy this from the
Help -> Info/About -> Copy
(Code -> About Visual Studio Code -> Copy
on macOS) option in Visual Studio Code: