Extension issue ""Cannot register 'redhat.telemetry.enabled'. This property is already registered."

[cforce]

• Issue Type: Bug
• Extension Name: vscode-yaml
• Extension Version: 0.21.1
• OS Version: Windows_NT x64 10.0.18363
• VS Code version: 1.58.2

{
	"messages": [
		{
			"type": 2,
			"message": "Cannot register 'redhat.telemetry.enabled'. This property is already registered.",
			"extensionId": {
				"value": "redhat.vscode-yaml",
				"_lower": "redhat.vscode-yaml"
			},
			"extensionPointId": "configuration"
		}
	],
	"activationTimes": {
		"codeLoadingTime": 3048,
		"activateCallTime": 1,
		"activateResolvedTime": 298,
		"activationReason": {
			"startup": false,
			"extensionId": {
				"value": "redhat.vscode-yaml",
				"_lower": "redhat.vscode-yaml"
			},
			"activationEvent": "onLanguage:yaml"
		}
	},
	"runtimeErrors": []
}

[ckeshava]

I have observed this issue in Mac OS also. Do you know of any workaround? Furthermore, this is causing the below error message for hitherto correctly working YAML files. Problems loading reference 'schemaservice:/path/to/schema.json': Unable to load schema from 'schemaservice:/path/to/schema.json': No content.YAML(768)

Are these two issues related?

[JPinkney]

Those issues don't seem to be related. Please file a new issue for that

[lego963]

Same here

• Issue Type: Bug
• Extension Name: vscode-yaml
• Extension Version: 0.22.0
• OS Version: Microsoft Windows 10 Pro 10.0.19043 N/A Build 19043
• VS Code version: 1.59.1

[marsfan]

I can also confirm it on windows 10. I suspect it is because I also have the XML extension from redhat, and they are using the same setting.

[tjx666]

Same here.

Version: 1.63.0-insider (Universal)
Commit: 3bd29c1d6c6ef5b6265614def99b7257b671ae19
Date: 2021-11-12T12:39:26.447Z
Electron: 13.5.2
Chromium: 91.0.4472.164
Node.js: 14.16.0
V8: 9.1.269.39-electron.0
OS: Darwin x64 21.1.0

[alcarcdr]

I also had this problem and after doing a few checks found that as @marsfan suggested it is being caused by the Red Hat XML having the same preference setting for telemetry. When XML is installed the YAML setting collides with it and triggers the warning[warning] [redhat.vscode-xml]: Cannot register 'redhat.telemetry.enabled'

I would consider it a minor bug if regardless of if XML or YAML set it it is still honoured by both. Yet I'm not sure if this is the case. It is somewhat more serious if the issue is causes one or the other to keep sending telemetry information when this should not (legally) happen. It might be worth fixing so as to reduce concerns it may not be behaving correctly.

[prettyv]

@AlanCarlyle To my understanding there is no reason why the setting wouldn't be honored by all extensions declaring and reading this setting equally regardless of which extension "won" the race to register the setting at startup. So this is I think mostly a cosmetic issue in that sense, but I also feel like the affected extensions should just use VS Code's preexisting global telemetry toggle and opened an issue in the shared telemetry library over here.

[metablaster]

I'm also having this issue with:

VSCode:

Version: 1.73.1 (system setup)
Commit: 6261075646f055b99068d3688932416f2346dd3b
Date: 2022-11-09T04:27:29.066Z
Electron: 19.0.17
Chromium: 102.0.5005.167
Node.js: 16.14.2
V8: 10.2.154.15-electron.0
OS: Windows_NT x64 10.0.19045
Sandboxed: No

YAML v1.10.1

I also have XML extension installed, and my telemetry option is set in user settings.

[robstryker]

Since no one has linked to the core issue where this was discussed, I'll go ahead and do that:

https://github.com/microsoft/vscode/issues/124662

It seems there's no way to hide the warning as of now. We might try to push for further enhancements in this regard.

[robstryker]

Are any of you all actually seeing a popup with this? Or are you just seeing it in your logs somewhere?

[marsfan]

@robstryker Its been a while, but I do remember seeing an actual popup in the bottom right corner of my window.