Skip to content

Extension activation failed under latest insiders build #20456

Closed

Description

Type: Bug

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)
GPU Status 2d_canvas: enabled
canvas_oop_rasterization: disabled_off
direct_rendering_display_compositor: disabled_off_ok
gpu_compositing: enabled
multiple_raster_threads: enabled_on
opengl: enabled_on
rasterization: enabled
raw_draw: disabled_off_ok
skia_renderer: enabled_on
video_decode: enabled
video_encode: enabled
vulkan: disabled_off
webgl: enabled
webgl2: enabled
webgpu: disabled_off
Load (avg) undefined
Memory (System) 11.70GB (2.67GB free)
Process Argv --crash-reporter-id 4285aea8-8024-49ba-97f2-9d60622a70f0
Screen Reader no
VM 0%
A/B Experiments
vsliv695:30137379
vsins829:30139715
vsliv368cf:30146710
vsreu685:30147344
python383cf:30185419
vspor879:30202332
vspor708:30202333
vspor363:30204092
vstes627:30244334
vslsvsres303:30308271
pythonvspyl392:30422396
pythontb:30258533
vsc_aacf:30263846
pythonptprofiler:30281269
vshan820:30294714
pythondataviewer:30285072
vscod805cf:30301675
bridge0708:30335490
bridge0723:30353136
cmake_vspar411:30581797
vsaa593cf:30376535
pythonvs932:30404738
cppdebug:30492333
vsclangdf:30492506
c4g48928:30535728
dsvsc012cf:30540253
pynewext54:30618038
pylantcb52:30590116
pyindex848:30611229
nodejswelcome1:30587009
pyind779:30611226
pythonsymbol12cf:30622697
fim-prod:30623723

Activity

  1. marcushallett commented on Jan 4, 2023

    @marcushallett

    I can confirm this happens on my machine as well.

  2. s1ssagar commented on Jan 4, 2023

    @s1ssagar

    Same facing this issue with the latest Insiders version.

    image

  3. marcushallett commented on Jan 4, 2023

    @marcushallett

    This is parallel to microsoft/vscode#170558.

  4. WitherZuo commented on Jan 4, 2023

    @WitherZuo

    Me too.

  5. Raphtor commented on Jan 4, 2023

    @Raphtor

    Disabling telemetry solved this for me (for now).

  6. Matheus-Garbelini commented on Jan 4, 2023

    @Matheus-Garbelini

    Raphael Norman-Tenazas (@Raphtor) indeed, disabling telemetry solved

  7. brettcannon commented on Jan 4, 2023

    @brettcannon
    Member

    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.

  8. added a commit that references this issue on Jan 4, 2023
    0aa1f37
  9. brettcannon commented on Jan 4, 2023

    @brettcannon
    Member

    FYI I have kicked off a build; I will update again once it's live on the Marketplace.

  10. brettcannon commented on Jan 4, 2023

    @brettcannon
    Member

    The new build is live! Once again, sorry about the bug.

  11. jchaidez-extron commented on Jan 4, 2023

    @jchaidez-extron

    Brett Cannon (@brettcannon)

    I am still experiencing this issue. How do I install the latest version?

  12. 4 remaining items

  13. jchaidez-extron commented on Jan 4, 2023

    @jchaidez-extron

    Brett Cannon (@brettcannon)

    prerelease

    I successfully updated and everything appears to be working.

  14. brettcannon commented on Jan 4, 2023

    @brettcannon
    Member

    jchaidez-extron thanks for the verification!

    And once again, sorry about the accidental breakage. 😅

  15. brettcannon commented on Jan 4, 2023

    @brettcannon
    Member

    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.

  16. chinmaykh commented on Jan 13, 2023

    @chinmaykh

    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?

  17. karthiknadig commented on Jan 13, 2023

    @karthiknadig
    Member

    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.

  18. jbolthouse commented on Jan 16, 2023

    @jbolthouse

    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...

  19. brettcannon commented on Jan 16, 2023

    @brettcannon
    Member

    Any pointers on how to get the pre-release to install on devcontainers?

    I'm not aware of any such mechanism, but I will ask the dev containers team and reply here if one happens to exist.

  20. chrmarti commented on Jan 17, 2023

    @chrmarti

    You can use "ms-python.python@prerelease" in the devcontainer.json:

    	"customizations": {
    		"vscode": {
    			"extensions": [
    				"ms-python.python@prerelease"
    			]
    		}
    	}

    This should work. The editor currently shows a warning, I need to update the JSON schema to allow for this.

  21. locked as resolved and limited conversation to collaborators on Feb 17, 2023
  22. added a commit that references this issue on May 22, 2024
    f6a0d45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

triage-neededNeeds assignment to the proper sub-team

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions