vscode-python: Extension 'ms-python.python' CANNOT use API proposal: telemetryLogger.
Type: Bug
I use the Pre-Release version of the extension. The latest release in this channel won’t load; you are directed to the developer tools which reports:
Activating extension 'ms-python.python' failed: Extension 'ms-python.python' CANNOT use API proposal: telemetryLogger.
Its package.json#enabledApiProposals-property declares: quickPickSortByLabel, testObserver but NOT telemetryLogger.
The missing proposal MUST be added and you must start in extension development mode or use the following command line switch: --enable-proposed-api ms-python.python.
Workaround: Switch to the release channel.
Extension version: 2022.19.13221011 VS Code version: Code 1.73.1 (6261075646f055b99068d3688932416f2346dd3b, 2022-11-09T02:22:48.959Z) OS version: Darwin arm64 21.6.0 Modes: Sandboxed: No Remote OS version: Linux x64 4.19.0-21-amd64
System Info
Item | Value |
---|---|
CPUs | Apple M1 Pro (10 x 24) |
GPU Status | 2d_canvas: enabled canvas_oop_rasterization: disabled_off direct_rendering_display_compositor: disabled_off_ok gpu_compositing: enabled metal: disabled_off 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) | 363, 692, 649 |
Memory (System) | 32.00GB (0.21GB free) |
Process Argv | –crash-reporter-id 6ee26e67-256e-4593-8cbb-57e7fb562f53 |
Screen Reader | no |
VM | 0% |
Item | Value |
---|---|
Remote | SSH: parsel |
OS | Linux x64 4.19.0-21-amd64 |
CPUs | AMD Turion™ II Neo N40L Dual-Core Processor (2 x 1500) |
Memory (System) | 5.70GB (3.70GB free) |
VM | 0% |
A/B Experiments
vsliv368cf:30146710
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
vslsvsres303:30308271
pythonvspyl392:30443607
vserr242:30382549
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
pythondataviewer:30285071
vscod805cf:30301675
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
cmake_vspar411:30581797
vsaa593cf:30376535
pythonvs932:30410667
cppdebug:30492333
vsclangdf:30486550
c4g48928:30535728
dsvsc012:30540252
azure-dev_surveyone:30548225
pyindex848cf:30577861
nodejswelcome1:30587005
fc301958:30595537
282f8724:30602487
gswce1:30612156
iaj6b796:30613358
dbltrim-noruby:30604474
f6dab269:30613381
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Reactions: 37
- Comments: 33 (11 by maintainers)
Commits related to this issue
- Bump VS Code engine to `1.74.0-insiders` Closes #20247 — committed to microsoft/vscode-python by brettcannon 2 years ago
- Bump VS Code engine to `1.74.0-insiders` (#20255) Closes #20247 — committed to microsoft/vscode-python by brettcannon 2 years ago
Workaround for Arch Adding some more context here for those who may not know how to apply the solutions given here:
yay code-features
"enable-proposed-api": ["ms-python.python"]
I’m also seeing this error pop up; code-oss version 1.74.0, extension v2022.20.0 - I tried adding the “enable-proposed-api”: [“ms-python.python”] line to argv.json and the issue wasn’t fixed.
EDIT: updating the code-features package from AUR resolved the issue.
I’ve also encountered this issue a few weeks ago, and I’m currently running Code OSS version
1.74.2
and python extensionv2022.20.1
.For me, editing
argv.json
didn’t do anything, functionality (as far as I can tell) remained identical with and without the line added. However, getting Code Features did the trick. Thanks everyone for providing insight and steps to fix this issue.I’m seeing this issue on 1.74
Version: 1.74.0 Commit: 5235c6bb189b60b01b1f49062f4ffa42384f8c91
Sorry about the mix-up, everyone! https://github.com/microsoft/vscode-python/pull/20255 will fix this, so the pre-release build that goes out tonight will restrict itself to VS Code 1.74.0-insiders.
@Saplyng well im on code-oss and just tried adding it to argv.json now and its fixed
@quinn-n if you’re using Arch then you are using Code - OSS and not the builds from code.visualstudio.com, so what people are suggesting above will cover your use case.
I confirm @AbdelrhmanNile that argv.json, “enable-proposed-api”: [“ms-python.python”], works. Stills with the same behavior as of 2022.20.1 as reported by @quinn-n .
Extensions were in auto update (2022.20.1) Code - OSS Version: 1.74.0 Commit: 5235c6bb189b60b01b1f49062f4ffa42384f8c91 Date: 2022-12-07T23:49:16.764Z Electron: 19.1.9 Chromium: 102.0.5005.167 Node.js: 16.14.2 V8: 10.2.154.15-electron.0 OS: Linux x64 6.0.12-arch1-1 Sandboxed: No
@munael It looks like your VS Code insiders build is from 2022-11-03 which might be too old even for the new API. Can you update to a newer VS Code insiders version (anything after 2022-11-16 is probably safe based on when the initial PR was created)? It’s working fine for me in the latest VS Code insiders so I can’t reproduce an issue.
I just uploaded 2022.19.13251009 which is actually the pre-release from Tuesday night/Wednesday morning, but with the version number bumped to be just after the one published this morning. Those on VS Code insiders will get the new release tonight, but everyone else on VS Code stable will sit on this release until you upgrade to VS Code 1.74.
FYI, we may have a solution, but we are still evaluating. Please stay subscribed to this issue and I will update if we manage to get things fixed for VS Code stable users (if you don’t hear from us assume the idea didn’t work and things will be back to normal once VS Code 1.74 is released).
@brettcannon It’s not critical, I’ll just have to remember to switch back to the pre-release channel once 1.74.0 becomes stable.