GitLens not loading for a single repository

[rajesh996]

Git lens is loading for all the different folders. But, it is not loading for a single folder. Why like that?

[eamodio]

@rajesh996 Can you provide more details? I'm not understanding the scenario that isn't working for you. Thanks!

[rajesh996]

I am using VSCode for my code development. And when I tried to use GitLens (installed the extension & reloaded VSCode). The GitLens sidebar doesn't show any files at all. It just keeps on loading, loading all the time. It's not working on one repository but working on another repository. I had removed the workspace settings and checked again but of no use.

[eamodio]

@rajesh996 Can you see if your issue is a casing issue like in #679?

[rajesh996]

yes, my issue is similar to the issue in #679.
GitLens worked with one repository and didn't work with other one in my issue

[eamodio]

@rajesh996 did you try any of the solutions to fix the issue with the repo it wasn't working with? For example, ensure that the casing you are open code with exactly matches the casing on disk. And/or change this git config setting: https://git-scm.com/docs/git-config#Documentation/git-config.txt-coreignoreCase?

[rajesh996]

Git Lens is not working on the particular folder in Ubuntu (only for that particular folder, with other folders it is working).
But, it is working perfectly on Windows for all the folders (including the one for which it is not working on Ubuntu).

[eamodio]

@rajesh996 For the folder that isn't working, are you sure you are opening the folder exactly as it appears on disk (no casing or other changes)?

[rajesh996]

@eamodio I have two folders in the untitled workspace in vscode. When I removed the folders (by keeping a file open), it worked. So, I removed all the folders and while closing Vscode, saved the workspace settings in some random place.
After that I again opened Vscode and added the folders one by one (in reverse order). Now, it is working fine.
Even now, the workspace is Untitled, but GitLens is working now.
Was that an issue of the workspace settings only.

[eamodio]

@rajesh996 so all is good now?

[rajesh996]

Yeah, but again today morning when I turned on my Ubuntu, the problem has crept in again. So, again I removed folders from the workspace, saved the settings and again opened it.
After this, it is working now. But, I am not getting what the issue was (that too, only for my PC it's coming. In other's PCs' it's working fine).

[PanosBougas]

I have a similar issue, GitLens constantly loading without doing anything. I am using GitLens on a remote VM through the Remote SSH extension (that means that GitLens is installed to the Remote machine). There I have opened a workspace which has 3 folders (panos, public, log). The first folder has a sub-folder named Foo with a git repo inside it. The second folder public has a repository too. The third folder does not contain any repo. The built-in VSCode GIT is working correctly and even the auto refresh works. Also, if I keep only the public folder in the workspace GitLens seems to be working, but that's an issue for me because I can't work without the other 2 folders.

This is the debug log in case it can provide some insight:

[2019-07-21 22:39:18:477] [2] GitService.getBuiltInGitApi
[2019-07-21 22:39:18:490] [2] GitService.getBuiltInGitApi completed • 13 ms
[2019-07-21 22:39:18:510] Git found: 2.21.0 @ /usr/bin/git • 19 ms
[2019-07-21 22:39:18:510] [1] GitService.initialize completed • 32 ms
[2019-07-21 22:39:18:511] Starting repository search in 3 folders
[2019-07-21 22:39:18:512] [3] GitService.repositorySearch(/home/panos) searching (depth=1)...
[2019-07-21 22:39:18:514] [4] LineAnnotationController.resume
[2019-07-21 22:39:18:515] [4] LineAnnotationController.resume completed • 0 ms
[2019-07-21 22:39:18:515] [5] LineAnnotationController.refresh
[2019-07-21 22:39:18:523] GitLens (v9.9.0) activated • 51 ms
[2019-07-21 22:39:18:523] [5] LineAnnotationController.refresh completed • 8 ms
[2019-07-21 22:39:18:526] [/home/panos] git rev-parse --show-toplevel • 14 ms 
[2019-07-21 22:39:28:241] [6] GitService.getOrderedRepositories
[2019-07-21 22:39:28:241] [7] GitService.getRepositories
[2019-07-21 22:39:28:492] [8] RepositoriesNode.onVisibilityChanged — e={"visible":true}
[2019-07-21 22:39:28:492] [9] RepositoriesNode.ensureSubscription
[2019-07-21 22:39:28:492] [a] RepositoriesNode.subscribe
[2019-07-21 22:39:28:492] [a] RepositoriesNode.subscribe completed • 0 ms
[2019-07-21 22:39:28:492] [b] RepositoriesNode.triggerChange
[2019-07-21 22:39:28:493] [c] RepositoriesView.refreshNode — e=RepositoriesNode, t=false
[2019-07-21 22:39:28:493] [d] RepositoriesNode.refresh — false
[2019-07-21 22:39:28:493] [8] RepositoriesNode.onVisibilityChanged completed • 0 ms
[2019-07-21 22:39:28:493] [e] FileHistoryTrackerNode.onVisibilityChanged — e={"visible":true}
[2019-07-21 22:39:28:493] [f] FileHistoryTrackerNode.ensureSubscription
[2019-07-21 22:39:28:493] [10] FileHistoryTrackerNode.subscribe
[2019-07-21 22:39:28:493] [10] FileHistoryTrackerNode.subscribe completed • 0 ms
[2019-07-21 22:39:28:493] [11] FileHistoryTrackerNode.triggerChange
[2019-07-21 22:39:28:493] [12] FileHistoryView.refreshNode — e=FileHistoryTrackerNode, t=false
[2019-07-21 22:39:28:493] [13] FileHistoryTrackerNode.refresh — false
[2019-07-21 22:39:28:493] [e] FileHistoryTrackerNode.onVisibilityChanged completed • 0 ms
[2019-07-21 22:39:28:493] [d] RepositoriesNode.refresh completed • 0 ms
[2019-07-21 22:39:28:493] [13] FileHistoryTrackerNode.refresh returned true • 0 ms
[2019-07-21 22:39:28:493] [14] RepositoriesView.triggerNodeChange — e=RepositoriesNode
[2019-07-21 22:39:28:494] [14] RepositoriesView.triggerNodeChange completed • 0 ms
[2019-07-21 22:39:28:494] [9] RepositoriesNode.ensureSubscription completed • 1 ms
[2019-07-21 22:39:28:494] [c] RepositoriesView.refreshNode completed • 1 ms
[2019-07-21 22:39:28:494] [b] RepositoriesNode.triggerChange completed • 1 ms
[2019-07-21 22:39:28:494] [f] FileHistoryTrackerNode.ensureSubscription completed • 1 ms
[2019-07-21 22:39:28:494] [12] FileHistoryView.refreshNode completed • 0 ms
[2019-07-21 22:39:28:494] [11] FileHistoryTrackerNode.triggerChange completed • 0 ms
[2019-07-21 22:39:28:494] [15] LineHistoryTrackerNode.onVisibilityChanged — e={"visible":true}
[2019-07-21 22:39:28:494] [16] LineHistoryTrackerNode.ensureSubscription
[2019-07-21 22:39:28:494] [17] LineHistoryTrackerNode.subscribe
[2019-07-21 22:39:28:494] [17] LineHistoryTrackerNode.subscribe completed • 0 ms
[2019-07-21 22:39:28:494] [18] LineHistoryTrackerNode.triggerChange
[2019-07-21 22:39:28:494] [19] LineHistoryView.refreshNode — e=LineHistoryTrackerNode, t=false
[2019-07-21 22:39:28:494] [1a] LineHistoryTrackerNode.refresh — false
[2019-07-21 22:39:28:494] [15] LineHistoryTrackerNode.onVisibilityChanged completed • 0 ms
[2019-07-21 22:39:28:494] [1a] LineHistoryTrackerNode.refresh returned true • 0 ms
[2019-07-21 22:39:28:494] [16] LineHistoryTrackerNode.ensureSubscription completed • 0 ms
[2019-07-21 22:39:28:494] [19] LineHistoryView.refreshNode completed • 0 ms
[2019-07-21 22:39:28:494] [18] LineHistoryTrackerNode.triggerChange completed • 0 ms```

Keep in mind that I haven't opened a file from my workspace and that log is created by simply opening the GitLens menu through the GitLens icon.

[rajesh996]

@PanosBougas once try changing the order in which you opened your folders. Not the best solution, but for me it is working after I changed the order in which the folders are opened, but the next day it is not working for me, so have to repeat the process everyday.