Open masoivn opened 3 years ago
I believe this is a known issue, regarding how VS Code deals with extensions contributing the same setting. We use vscode-redhat-telemetry for optional telemetry, and as per https://github.com/redhat-developer/vscode-redhat-telemetry#contribute-the-redhattelemetryenabled-preference , we define the setting in our package.json. However, if other extensions also define it, then this is where that warning is coming from. I don't believe it affects the functionality of anything, but simply fails to register the property as there is no need.
Do you have other extensions such as vscode-java, vscode-yaml, vscode-quarkus that might also have support for the same capability ?
VS Code reports the extension as unresponsive on the running extensions page, at the same time it also says that the extension couldn't register this property, so I can't help but wonder if this error has anything to do with that?
In my case, I occasionally see the warning as a notification and other times not. However I consistently see it in the running extensions page. The extension itself does activate without issue though. @angelozerr are you able to reproduce the unresponsive behaviour ?
The additional extensions I needed to produce this were from Quarkus, which I installed first.
Bug
vscode-xml
0.18.0
Windows_NT x64 10.0.19042
1.59.1
:warning: We have written the needed data into your clipboard. Please paste! :warning:
Errors: Cannot register 'redhat.telemtry.enabled'. This property is alerady registered.