Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TreeError [latex-workshop-structure] Data tree node not found: [object Object] #160575

Closed
VSCodeTriageBot opened this issue Sep 9, 2022 · 0 comments · Fixed by #160784
Closed
Assignees
Labels
error-telemetry VS Code - Issues generated by telemetry insiders-released Patch has been released in VS Code Insiders

Comments

@VSCodeTriageBot
Copy link
Collaborator

Error: TreeError [latex-workshop-structure] Data tree node not found: [object Object]
at de.getDataNode in src/vs/base/browser/ui/tree/asyncDataTree.ts:721:10
at de.expand in src/vs/base/browser/ui/tree/asyncDataTree.ts:580:21
at process.processTicksAndRejections (node:internal/process/task_queues:96:5)
at async Promise.all (index 0)
at async ge.expand in src/vs/workbench/browser/parts/views/treeView.ts:788:4
at async S.reveal in src/vs/workbench/api/browser/mainThreadTreeViews.ts:141:5

Go to Errors Site

@VSCodeTriageBot VSCodeTriageBot added the error-telemetry VS Code - Issues generated by telemetry label Sep 9, 2022
@alexr00 alexr00 added this to the September 2022 milestone Sep 13, 2022
@VSCodeTriageBot VSCodeTriageBot added unreleased Patch has not yet been released in VS Code Insiders insiders-released Patch has been released in VS Code Insiders and removed unreleased Patch has not yet been released in VS Code Insiders labels Sep 13, 2022
@github-actions github-actions bot locked and limited conversation to collaborators Oct 28, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
error-telemetry VS Code - Issues generated by telemetry insiders-released Patch has been released in VS Code Insiders
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants