redhat-developer / redhat-developer/vscode-yaml
Extension issue ""Cannot register 'redhat.telemetry.enabled'. This property is already registered."
Open
Nobody has claimed this yet.
bug
upstream
- Dominant language
- TypeScript
- Stars
- 829
- Forks
- 260
- Avg merge
- 5h 43m
- Merged PRs (30d)
- 1
Description
- 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": []
}
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the duplicate configuration-registration error with vscode-yaml 0.21.1 on the reported VS Code and Windows versions, then trace where redhat.telemetry.enabled is registered. Done means the extension activates for YAML without reporting that the property is already registered.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100