You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Extension activation failed under latest insiders build #20456
A few hours ago VSC was updated to the latest insiders build and upon restart the Python extension fails to load with the following error message being shown in the Developer Tools console:
Activating extension 'ms-python.python' failed: this.a.sendEventData is not a function.
$onExtensionActivationError @ mainThreadExtensionService.ts:111
Extension version: 2022.21.13601008
VS Code version: Code - Insiders 1.75.0-insider (4acf2d9, 2023-01-04T07:12:58.785Z)
OS version: Windows_NT x64 10.0.22621
Modes:
Sandboxed: Yes
System Info
Item
Value
CPUs
Intel(R) Core(TM) i5-1035G1 CPU @ 1.00GHz (8 x 1190)
Sorry about this, everyone! There was a miscommunication over who was going to bump a npm dependency to handle microsoft/vscode@4acf2d9 . We will get a fix in today and we will update here once the build has gone live.
And for those that turned off telemetry to work around this, if you're comfortable with turning it back on, we would appreciate it if you could turn telemetry back on. We try to be data-driven and so telemetry is important, especially from our pre-release users as it's how we know whether something is an improvement or detriment to folks upfront before we roll it out to stable.
And just as a general FYI, thanks to all of you for being pre-release users! We do appreciate the help and support in testing stuff early to provide us feedback on things.
Chinmay K Haritas (@chinmaykh) you should be able to do this from the extension view from VS Code. Click on the python extension, then select install pre-release. That should get you the latest pre-release.
Any pointers on how to get the pre-release to install on devcontainers? I have been able to get python to load by manually clicking the switch button in the remote container context. But it will not reload pylance without a restart-rebuild. But when I do that python fails again...
Activity
marcushallett commentedon Jan 4, 2023
I can confirm this happens on my machine as well.
s1ssagar commentedon Jan 4, 2023
Same facing this issue with the latest Insiders version.
marcushallett commentedon Jan 4, 2023
This is parallel to microsoft/vscode#170558.
WitherZuo commentedon Jan 4, 2023
Me too.
Raphtor commentedon Jan 4, 2023
Disabling telemetry solved this for me (for now).
Matheus-Garbelini commentedon Jan 4, 2023
Raphael Norman-Tenazas (@Raphtor) indeed, disabling telemetry solved
brettcannon commentedon Jan 4, 2023
Sorry about this, everyone! There was a miscommunication over who was going to bump a npm dependency to handle microsoft/vscode@4acf2d9 . We will get a fix in today and we will update here once the build has gone live.
Bump extension/telemetry version
brettcannon commentedon Jan 4, 2023
FYI I have kicked off a build; I will update again once it's live on the Marketplace.
brettcannon commentedon Jan 4, 2023
The new build is live! Once again, sorry about the bug.
jchaidez-extron commentedon Jan 4, 2023
Brett Cannon (@brettcannon)
I am still experiencing this issue. How do I install the latest version?
4 remaining items
Bump the major version number to 2023
Bump the major version to 2023 (#20465)
jchaidez-extron commentedon Jan 4, 2023
Brett Cannon (@brettcannon)
I successfully updated and everything appears to be working.
brettcannon commentedon Jan 4, 2023
jchaidez-extron thanks for the verification!
And once again, sorry about the accidental breakage. 😅
brettcannon commentedon Jan 4, 2023
And for those that turned off telemetry to work around this, if you're comfortable with turning it back on, we would appreciate it if you could turn telemetry back on. We try to be data-driven and so telemetry is important, especially from our pre-release users as it's how we know whether something is an improvement or detriment to folks upfront before we roll it out to stable.
And just as a general FYI, thanks to all of you for being pre-release users! We do appreciate the help and support in testing stuff early to provide us feedback on things.
chinmaykh commentedon Jan 13, 2023
Hi, still unsure how to get the latest build. Checking for updates says I'm up to date and I don't know how to remove telemetry! Help please?
karthiknadig commentedon Jan 13, 2023
Chinmay K Haritas (@chinmaykh) you should be able to do this from the extension view from VS Code. Click on the python extension, then select install pre-release. That should get you the latest pre-release.
jbolthouse commentedon Jan 16, 2023
Any pointers on how to get the pre-release to install on devcontainers? I have been able to get python to load by manually clicking the switch button in the remote container context. But it will not reload pylance without a restart-rebuild. But when I do that python fails again...
brettcannon commentedon Jan 16, 2023
I'm not aware of any such mechanism, but I will ask the dev containers team and reply here if one happens to exist.
chrmarti commentedon Jan 17, 2023
You can use
"ms-python.python@prerelease"in the devcontainer.json:This should work. The editor currently shows a warning, I need to update the JSON schema to allow for this.
Merged PR posit-dev/positron-python#14: Merge upstream of vscode pyth…
Merged PR posit-dev/positron-python#14: Merge upstream of vscode pyth…
Bump extension/telemetry dependency version (microsoft#20462)