vscode: 'Reveal in sidebar` does not work

Issue Type: Bug

  ERR Data tree node not found: [object Object]: Error: Data tree node not found: [object Object]
    at i.e.getDataNode (file:///Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:1037:175)
    at i.<anonymous> (file:///Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:1034:638)
    at file:///Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:33:935
    at Object.next (file:///Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:34:33)
    at file:///Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:33:160
    at new Promise (<anonymous>)
    at i (file:///Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:32:952)
    at i.e.expand (file:///Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:1034:277)
    at Array.<anonymous> (file:///Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:5626:80)
    at t (file:///Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:105:891)
log.ts:173   ERR An unknown error occurred. Please consult the log for more details.

Actual: file could not be found in the sidebar Expected: active file shows in the sidebar

Notes: after reboot VS code reveal in sidebar works but after some time it stops working

VS Code version: Code 1.31.0 (7c66f58312b48ed8ca4e387ebd9ffe9605332caa, 2019-02-05T22:32:14.164Z) OS version: Darwin x64 18.2.0

System Info
Item Value
CPUs Intel® Core™ i5-8259U CPU @ 2.30GHz (8 x 2300)
GPU Status 2d_canvas: enabled
checker_imaging: disabled_off
flash_3d: enabled
flash_stage3d: enabled
flash_stage3d_baseline: enabled
gpu_compositing: enabled
multiple_raster_threads: enabled_on
native_gpu_memory_buffers: enabled
rasterization: enabled
surface_synchronization: enabled_on
video_decode: enabled
webgl: enabled
webgl2: enabled
Load (avg) 2, 2, 2
Memory (System) 16.00GB (0.72GB free)
Process Argv
Screen Reader no
VM 0%
Extensions (47)
Extension Author (truncated) Version
mithril-emmet Fal 0.7.1
vscode-javascript-snippet-pack aka 0.1.5
project-manager ale 10.3.2
solargraph cas 0.19.3
turbo-console-log Cha 1.2.13
path-intellisense chr 1.4.2
bracket-pair-colorizer Coe 1.0.61
cjsx cri 0.0.6
vscode-svgviewer css 1.4.7
vscode-faker dee 1.3.0
githistory don 0.4.6
gitlens eam 9.5.0
remotehub eam 0.2.0
EditorConfig Edi 0.12.8
prettier-vscode esb 1.8.1
nasc-touchbar fel 1.11.0
auto-close-tag for 0.5.6
auto-rename-tag for 0.0.15
vscode-flow-ide gca 1.2.0
vscode-pull-request-github Git 0.4.0
gc-excelviewer Gra 2.1.28
haml kar 1.1.0
ruby-syntax-replacer Kos 1.0.11
restructuredtext lex 103.0.0
atom-keybindings ms- 3.0.6
debugger-for-chrome msj 4.11.1
language-liquid nei 0.1.1
vetur oct 0.15.0
vscode-docker Pet 0.5.2
material-icon-theme PKi 3.6.3
vscode-css-peek pra 2.2.0
ruby reb 0.21.0
vscode-icons rob 8.1.0
sass-indented rob 1.5.1
code-settings-sync Sha 3.2.4
autoimport ste 1.5.3
code-spell-checker str 1.6.10
lodash-snippets tom 1.0.0
gitblame wad 2.6.3
vscode-wakatime Wak 1.2.5
quokka-vscode Wal 1.0.182
vscode-import-cost wix 2.12.0
change-case wma 1.0.0
JavaScriptSnippets xab 1.7.2
ReactSnippets xab 2.3.0
html-css-class-completion Zig 1.18.0
vscode-open-in-github ziy 1.3.6

(3 theme extensions excluded)

About this issue

  • Original URL
  • State: closed
  • Created 5 years ago
  • Reactions: 26
  • Comments: 27 (9 by maintainers)

Most upvoted comments

While in waiting for fixes in next version or insider This little dude is da real MVP, fixes your tree like a pro

screenshot from 2019-02-28 16-05-25

Tomorrow’s vscode insiders will contain the fix. Try it out and let us know how it behaves for you.

The issue was that the explorer was trying to be smart and figure out which exact part of the tree to refresh on raw file event. Howeever since there can be many events sometimes it is better to just refresh the whole tree (which was the previous strategy). So I decided to go back to the old approach

It happens to me every time I run a script (probably because it’s altering the tree). The problem is temporarily fixed if I simply cmd + , and close it (probably because it refreshes something), until I run any script again (like my building process, so you can imagine this happens all the time and is very annoying hehe)

Same erratic behavior with latest 1.31.1.

@isidorn have you guys tried to run some kind of building process? Something like npm start in a React project, or any webpack configuration that changes files in the files tree. I’m pretty sure the problem happens because of that since there are reports of it happening on branch change too.

For me it happens 100% of the times I run a build script, one is using a custom script to build a Roku package, and the other is when running npm start or similar in a wordpress with sage theme. Also it always resolves the problem by just opening and closing the options tab.