Extension 'ms-python.python' CANNOT use API proposal: telemetryLogger.

[mjpieters]

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(tm) 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

[karrtikr]

@lramos15 Can you please look into it?

[ldeluigi]

I confirm that this error occurs.

[rnwang04]

I meet this error too.

[lramos15]

@karrtikr This is because we're mixing stable VS Code with pre-release python. Stable VS Code does not have proposed access for Python yet for this API since we have not completed a new release since adopting this API. What we want here is to actually bump the engine to prevent pre-release Python from running on stable

[brettcannon]

Sorry about the mix-up, everyone! #20255 will fix this, so the pre-release build that goes out tonight will restrict itself to VS Code 1.74.0-insiders.

[mjpieters]

What does that mean for those sticking to 1.73.0? Will there be a pre-release build to switch back to?

[brettcannon]

@mjpieters I'll have to think through if there's a way to fix that, but it's possible we can't (at least not easily, especially with half the team out on holidays and that include the half who typically handle our publishing pipelines). Our pre-releases are automatically released as part of an internal pipeline, and the only way to get around it to fix this for folks on stable I think would be to go back to the commit before the proposed API was first used, tweak the version to somehow squeeze in between yesterday and today's automatic release, and then manually trigger the build.

[mjpieters]

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

[brettcannon]

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]

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.

[munael]

I'm on 2022.19.13321005 and the issue persists :/
VSC:

Version: 1.74.0-insider (user setup)
Commit: e8eb39bac26ddc87f27ed69fa06c54cd230d18f9
Date: 2022-11-03T18:43:35.409Z
Electron: 19.1.3
Chromium: 102.0.5005.167
Node.js: 16.14.2
V8: 10.2.154.15-electron.0
OS: Windows_NT x64 10.0.19044
Sandboxed: Yes

EDIT: Updating VS Code seems to fix it.

[brettcannon]

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

[tonescones]

I'm seeing this issue on 1.74

Version: 1.74.0
Commit: 5235c6bb189b60b01b1f49062f4ffa42384f8c91

[AbdelrhmanNile]

im seeing it too on 1.74.0
1.74.0
5235c6bb189b60b01b1f49062f4ffa42384f8c91
x64

[quinn-n]

I'm seeing it on 1.74.0 too

[brettcannon]

@tonescones @AbdelrhmanNile @quinn-n what version of the extension do you have installed?

[brettcannon]

And to make sure, you are using VS Code and not VSCodium?

[Saplyng]

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.

[AbdelrhmanNile]

@Saplyng well im on code-oss and just tried adding it to argv.json now and its fixed

[quinn-n]

@brettcannon I get the error on v2022.20.0 and v2022.20.1. I'm on Code not Codium.

[alegtk]

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

[brettcannon]

@quinn-n Assuming you're using VS Code as downloaded from code.visualstudio.com, can you open a new issue using the Report Issue command, as you seem to be unique in your failure?

Otherwise it seems everyone else on this issue is using a build not downloaded from code.visualstudio.com and thus have to opt into the proposed API we are currently using, so I will consider this resolved for everyone else. Thanks to everyone helping each other out to figure out the solution!

[quinn-n]

@brettcannon I'm using the arch package. I haven't tried changing argv.json yet. I'll give it a shot when I get a chance.

[brettcannon]

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

[ThatCooperLewis]

Workaround for Arch
Adding some more context here for those who may not know how to apply the solutions given here:

• Install/update code-features
  yay code-features
• In VSCode, Shift-Ctrl-P > "Configure Runtime Arguments" > Add this line:
  "enable-proposed-api": ["ms-python.python"]

[quinn-n]

The "enable-proposed-api": ["ms-python.python"] solution worked for me. Thanks all

[brettcannon]

MS broke this on purpose with no regards to the community builds.

To be clear, this was not done on purpose to break anyone and I don't know how that conclusion was reached to begin with. It just so happens to be something that requires folks using a different build of VS Code to add a configuration flag to make it work. This has never been an issue with any other proposed API that we have used (and we have three going right now), so this was unexpected for us. This also wasn't reported by anyone using the pre-release of the Python extension, so this was not reported to us until after the stable release had gone out. Had we known this was going to happen we probably would have at least put a warning about it in our blog post on how to fix it. But as I said, we just didn't know this issue would occur.

[Howardohyea]

I've also encountered this issue a few weeks ago, and I'm currently running Code OSS version 1.74.2 and python extension v2022.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.

[radupotop]

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.

This is exactly the sort of issue I was referring to. The extension cannot just be re-enabled with a flag in argv.json, but instead relies on the community to provide an arcane patch of /usr/lib/code/product.json.

[Howardohyea]

This is exactly the sort of issue I was referring to. The extension cannot just be re-enabled with a flag in argv.json, but instead relies on the community to provide an arcane patch of /usr/lib/code/product.json.

Out of curiosity, if the extension can't be re-enabled with that edit to argv.json, how did the others manage to fix it? Or am I just the edge case?

[clbs]

Workaround for Arch

This fixed my install with code - oss

[asdrubalivan]

Workaround for Arch Adding some more context here for those who may not know how to apply the solutions given here:

I can confirm that this works for Manjaro as well