redhat-developer / redhat-developer/vscode-xml
TypeError thrown in extension host logs
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 328
- Forks
- 101
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 7
Description
2025-04-30 14:03:58.616 [error] [redhat.vscode-xml] provider FAILED
2025-04-30 14:03:58.616 [error] TypeError: Cannot read properties of null (reading 'tags')
at Object.asCompletionItem (/home/davthomp/Documents/Projects/vscode-xml/dist/extension.js:37097:48)
at /home/davthomp/Documents/Projects/vscode-xml/dist/extension.js:32898:66
at async SD.resolveCompletionItem (file:///usr/share/code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:135:146164)
Based on this logs I thought it might have something to do with how we're converting protocol completion items to VS Code completion items. However, as far as I can tell we're just using the built in functionality of the language client to do this. This requires further investigation.
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 with the logged stack trace, especially asCompletionItem in dist/extension.js and the language client's protocol-to-VS Code completion-item conversion mentioned in the report. Reproduce the completion-item resolution path and determine why a null value is accessed while reading tags. Done means the cause is identified and the TypeError no longer occurs in the affected extension-host flow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100