Git - diff editor cannot be opened while scanning for repositories
See original GitHub issueDoes this issue occur when all extensions are disabled?: Yes
- VS Code Version: 1.72.2
- OS Version: Windows 10
Steps to Reproduce:
I can consistently reproduce the issue only for a specific repository (microsoft/vcpkg) but I highly doubt that it is reproducible elsewhere… Maybe it is worth noting that I didn’t use code with this repository for a long time.
The consequence is that I can’t look at diffs or history because they are loading a few minutes and work only if the spam stops at the git output.
Issue Analytics
- State:
- Created a year ago
- Reactions:1
- Comments:6 (3 by maintainers)
Top Results From Across the Web
git difftool, open all diff files immediately, not in serial
I'm looking for a way to open all the files at once - in BeyondCompare for example this would open all the files...
Read more >Setting up code scanning for a repository - GitHub Docs
Code scanning is available for organization-owned repositories in GitHub Enterprise Server. This feature requires a license for GitHub Advanced Security.
Read more >Git error - Fatal: Not a git repository and how to fix it | Datree.io
A Git command needs to be run on a specific repository, so this error typically occurs when a Git command is run in...
Read more >git-status Documentation - Git
When "untracked" is used submodules are not considered dirty when they only contain untracked content (but they are still scanned for modified content)....
Read more >Web IDE - GitLab Documentation
When viewing a file or the repository file list · Select the ( ) next to Edit or Gitpod, depending on your configuration....
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Sounds great!
I think you should be able to reproduce the problem on any JS project with a large
node_modules
if you removenode_modules
fromgit.repositoryScanIgnoredFolders
and setgit.repositoryScanMaxDepth
to 5.Thanks! I will try to set up a repro and see if I am able to reproduce the problem.