Folder in workspace not showing files underneath it

[penguin2839]

Issue Type: Bug

When using a workspace I have a folder that doens't show files underneath it when I expand the folder. The files exist on the file system and i can manually open the file using file->open file.

VS Code version: Code 1.37.0 (036a6b1, 2019-08-08T02:33:50.993Z)
OS version: Windows_NT x64 10.0.17134
Remote OS version: Linux x64 3.10.0-957.10.1.el7.x86_64

System Info

Item	Value
CPUs	Intel(R) Core(TM) i7-8650U CPU @ 1.90GHz (8 x 2112)
GPU Status	2d_canvas: enabled flash_3d: enabled flash_stage3d: enabled flash_stage3d_baseline: enabled gpu_compositing: enabled multiple_raster_threads: enabled_on native_gpu_memory_buffers: disabled_software oop_rasterization: disabled_off protected_video_decode: enabled rasterization: enabled skia_deferred_display_list: disabled_off skia_renderer: disabled_off surface_synchronization: enabled_on video_decode: enabled viz_display_compositor: disabled_off webgl: enabled webgl2: enabled
Load (avg)	undefined
Memory (System)	15.85GB (8.60GB free)
Process Argv
Screen Reader	no
VM	0%

Item	Value
Remote	SSH: vmlxrndckt02
OS	Linux x64 3.10.0-957.10.1.el7.x86_64
CPUs	Intel(R) Xeon(R) CPU E5-2690 v4 @ 2.60GHz (2 x 2593)
Memory (System)	3.84GB (0.23GB free)
VM	100%

Extensions (4)

Extension	Author (truncated)	Version
remote-ssh	ms-	0.45.5
remote-ssh-edit	ms-	0.45.5
remote-ssh-explorer	ms-	0.45.5
python	ms-	2019.8.30787

[gjsjohnmurray]

My guess is, you have a files.exclude setting that's making those files be hidden in Explorer.

[gjsjohnmurray]

See https://stackoverflow.com/questions/30140112/how-do-i-hide-certain-files-from-the-sidebar-in-visual-studio-code

[vscodebot]

Please ask your question on StackOverflow. We have a great community over there. They have already answered thousands of questions and are happy to answer yours as well. See also our issue reporting guidelines.

Happy Coding!

[penguin2839]

I don’t appear to have a files.exclude setting applied.

[gjsjohnmurray]

So maybe #78743 which will be fixed in the upcoming 1.37.1 recovery release.