-
Notifications
You must be signed in to change notification settings - Fork 132
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
EACCES error on directory w/o permissoins #223
Comments
I also encountered EACCESS. I want you to ignore EACCESS and continue scanning. In my case, I could not access because the directory to be scanned is owned by root:root.
miwa@archlinux[~/work/xxxx]% sudo ls -l root
total 40
drwxr-xr-x 2 root root 36864 Apr 16 15:26 aaaa
drwxr-xr-x 2 root root 4096 Apr 16 15:26 bbbb |
Thanks for reporting this. #224 fixes the issue by not crashing the server but skips cross-file references. There is also a warning encouraging you to update the glob or fix permission issues. Hope this solves the issue for you. |
I'm not sure how to update the glob in the VS Code extension to exclude that directory; I tried excluding it from the editor using |
@jordemort fair point. I figured out a way to handle this case by letting the globbing library run in non-strict mode. |
A fix has been released, a new server and vscode client is out. Let me know if it works for you. |
Yes, it is working for me now. Thank you! |
Similar to #202
I'm using VS Code's Remote SSH functionality to connect to a development server that keeps my workspace mounted on its own file system. Unfortunately, that means my workspace contains a
lost+found
directory that I don't have permission to read. This leads to the extension failing to start with:The text was updated successfully, but these errors were encountered: