Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] 0.2.0 does not include metadata.json in extension payload #147

Open
Glutnix opened this issue May 26, 2024 · 1 comment
Open

[BUG] 0.2.0 does not include metadata.json in extension payload #147

Glutnix opened this issue May 26, 2024 · 1 comment
Labels
bug Something isn't working

Comments

@Glutnix
Copy link

Glutnix commented May 26, 2024

Got this error in the Extension Host output panel:

2024-05-26 22:28:58.932 [error] Activating extension joedevivo.vscode-circuitpython failed due to an error:
2024-05-26 22:28:58.932 [error] Error: ENOENT: no such file or directory, open 'c:\Users\brett\.vscode\extensions\joedevivo.vscode-circuitpython-0.2.0-win32-x64\boards\metadata.json'
	at Object.openSync (node:fs:605:3)
	at Object.func [as openSync] (node:electron/js2c/node_init:2:2214)
	at Object.readFileSync (node:fs:473:35)
	at t.readFileSync (node:electron/js2c/node_init:2:9771)
	at Board.loadBoards (c:\Users\brett\.vscode\extensions\joedevivo.vscode-circuitpython-0.2.0-win32-x64\out\boards\board.js:24:27)
	at new Container (c:\Users\brett\.vscode\extensions\joedevivo.vscode-circuitpython-0.2.0-win32-x64\out\container.js:27:23)
	at Container.newInstance (c:\Users\brett\.vscode\extensions\joedevivo.vscode-circuitpython-0.2.0-win32-x64\out\container.js:14:35)
	at activate (c:\Users\brett\.vscode\extensions\joedevivo.vscode-circuitpython-0.2.0-win32-x64\out\extension.js:13:49)
	at Z.kb (c:\Program Files\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:159:13465)
	at Z.jb (c:\Program Files\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:159:13175)
	at c:\Program Files\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:159:11197
	at async h.n (c:\Program Files\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:143:6281)
	at async h.m (c:\Program Files\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:143:6244)
	at async h.l (c:\Program Files\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:143:5701)

I checked, yes, metadata.json is not present in that folder.

When trying to invoke the 'CircuitPython: Check for latest bundle' command I get:

[Window Title]
Visual Studio Code

[Main Instruction]
Command 'CircuitPython: Check for latest bundle' resulted in an error

[Content]
command 'circuitpython.library.fetch' not found

[OK]

I am using joedevivo.vscode-circuitpython v0.2.0 as found on the marketplace.
Latest Windows 11. Mu Editor has no problem listening and talking to the device over serial.

I have a Raspberry Pi Pico H (2021) with adafruit-circuitpython-raspberry_pi_pico-en_GB-9.0.5.uf2 installed.
usbview.exe reports:

idVendor:                        0x239A = Adafruit Industries LLC
idProduct:                       0x80F4
bcdDevice:                       0x0100
iManufacturer:                     0x01
     English (United States)  "Raspberry Pi"
iProduct:                          0x02
     English (United States)  "Pico"
iSerialNumber:                     0x03
     English (United States)  "XXXXXXXXXXXXXXXX"

And FWIW, I can't find a board that matches that vendor/product id within the boards folder of the extension. I see 0x239A/0x80F2 which seems close. shrug

@Glutnix Glutnix added the bug Something isn't working label May 26, 2024
@moviebrain
Copy link

Go into the vscode extension page and find the “install previous version” and install .19 or whatever was just before .20, it fixed my problems. Something about the way the extension is compiled doesn’t let it work with the most up to date version of Electron that vscode is based on, but .19 is just fine.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants