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] no comands are found #141

Open
hunter72007 opened this issue Feb 11, 2024 · 8 comments
Open

[BUG] no comands are found #141

hunter72007 opened this issue Feb 11, 2024 · 8 comments
Labels
bug Something isn't working

Comments

@hunter72007
Copy link

Navigate to your workspace.
Press Ctrl+Shift+P.
Attempt to run any CircuitPython command.
Observe the error.
Expected behavior
When attempting to run any command, I expect to receive a "command not found" error.

Screenshots
Screenshot

OS: Windows 11

@hunter72007 hunter72007 added the bug Something isn't working label Feb 11, 2024
@shanselman
Copy link

Seeing this also @joedevivo

@arthurolivierfortin
Copy link

got the same problem..

@dustinlacewell
Copy link

This seems pretty blocking.,,

@HarisM26
Copy link

had this problem today

@scottpletcher
Copy link

Just started occurring for me this evening after, strangely, a week of flawless developing. The only thing that I did was flash my Feather ESP32-S2 to CircuitPython 9.0.0. That seemed to be the activity that started this. Even tried to revert to 8.x..now not really sure what might have happened with either VSCode or my Feather. Running VSCode 1.87.2 on Fedora 39 Silverblue (RPM install and not the Flatpak).

@scottpletcher
Copy link

I seemed to have got rid of this issue by reverting back to v0.1.2, restarting VSCode and then upgrading again to v0.2.0. 🤞

@Sola85
Copy link

Sola85 commented Apr 15, 2024

Also facing this issue. Switching back to v0.1.20 seems to fix the issues for now.

@cybermanhao
Copy link

same question,in windows11,i have use this extention correctly for 2days,but now this occured.
tring to install v0.1.2 and update solved it and then crashed again.
this time install v0.1.2 and update didnt solve it.

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

8 participants