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

file explorer doesn't show anything in large git repo's #78910

Closed
MuhsinFatih opened this issue Aug 11, 2019 · 4 comments
Closed

file explorer doesn't show anything in large git repo's #78910

MuhsinFatih opened this issue Aug 11, 2019 · 4 comments
Assignees
Labels
*duplicate Issue identified as a duplicate of another issue(s) info-needed Issue requires more information from poster

Comments

@MuhsinFatih
Copy link

  • VSCode Version: 1.37 (July update)
  • OS Version: MacOS Mojave 10.14.6 (18G87)

Steps to Reproduce:

  1. open a large git repo in vscode

Result: Explorer will not display anything, but files are accessible (i.e.: I can open files with quickopen, edit them as usual)

Does this issue occur when all extensions are disabled?: Yes

I also installed the insiders version today (Version: 1.37.0-insider), seems to be the same version, and issue still occurs there.
I rolled back to 1.36.1, and it works as expected in this version

@bpasero
Copy link
Member

bpasero commented Aug 12, 2019

@MuhsinFatih is that on a remote network drive? Are you having dangling symbolic links within? Does it reproduce with our Exploration builds that use a newer node.js version?

Download:

@bpasero bpasero added the info-needed Issue requires more information from poster label Aug 12, 2019
@MuhsinFatih
Copy link
Author

Yes, sorry for not mentioning those. It's actually exactly like that: a remote folder with dangling symlinks. I'm using sshfs, so although they are in fact not dangling symlinks, since I don't have access to their realpath's locally, to vscode they are dangling.
I don't know about exploration builds, I'll check that when I get the chance

@bpasero
Copy link
Member

bpasero commented Aug 12, 2019

/duplicate #78743

@vscodebot vscodebot bot added the *duplicate Issue identified as a duplicate of another issue(s) label Aug 12, 2019
@vscodebot
Copy link

vscodebot bot commented Aug 12, 2019

Thanks for creating this issue! We figured it's covering the same as another one we already have. Thus, we closed this one as a duplicate. You can search for existing issues here. See also our issue reporting guidelines.

Happy Coding!

@vscodebot vscodebot bot closed this as completed Aug 12, 2019
@vscodebot vscodebot bot locked and limited conversation to collaborators Sep 26, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
*duplicate Issue identified as a duplicate of another issue(s) info-needed Issue requires more information from poster
Projects
None yet
Development

No branches or pull requests

3 participants