Replies: 2 comments 3 replies
-
Do you have any idea how the |
Beta Was this translation helpful? Give feedback.
-
Hi @code-asher , I believe that I do have more information though. It appears that it was a mounting issue from s3fs-fuse which caused some folders to appear that way. We switched to goofys for some testing and no longer get that issue were a folder/directory has I'm not sure if there is a way to replicate creating a folder with |
Beta Was this translation helpful? Give feedback.
-
Hi,
I recently attempted to upgrade to code-server 3.5.0 (and before this to code-server 3.4.1), from code-server version 2.1692-vsc1.39.2. With both versions I had picked that my mounted (fusermount) directories where available in the explorer, but when I clicked the directory it did not show the contents of the folder. I was however able to run
ls
in the terminal and see the contents of the mounted directory. There was no error in the logs why the mounted directory did not show the contents.A bit of investigation today relieved a bit more when I ran
ls -la
on the mounted directory.As you can see from the screenshot, there is folder/directory that appears to be at fault. Once I ran
mkdir tf
, the VS Code explorer was able to show the contents of the mounted directory. So I guess in the older version of code-server, the explorer was failing silently and not showing the faulty foldertf
, but now with newer releases the entire mounted directory is failing to show.My first question would be, is there a property I can set that will ignore future cases were code-server can fail silently on faulty folders and show the entire mounted directory? If not, can this be reported as bug instead in order to get it fix?
Beta Was this translation helpful? Give feedback.
All reactions