Vscode-gitlens: Regression: Submodules don't work properly (missing repo in view, file and inline blame, etc)
- GitLens Version: 9.0.1
- VSCode Version: 1.29.1
- OS Version: CentOS 7
After the extension updated today, I noticed some issues with git blame: I don't see the inline blame annotation, (I tried to toggle it to no avail), and the "File Blame Annotations" command is missing. Is this intentional?
tianbis
All 19 comments
@eltian Definitely not intentional.
Can you please enable output channel logging by setting "gitlens.outputLevel": "debug" in your settings.json. This will enable logging to the GitLens channel in the Output pane. Once enabled, please reproduce the issue (if possible) and attach the log lines from the GitLens channel.
eamodio
on 3 Dec 2018
Here's the debug output for gitlens. Keep it mind that, although we're working with an older version of git (1.8), these features were still working as of last week:
[2018-12-03 17:57:12:033] [1] GitService.initialize
[2018-12-03 17:57:12:607] Git found: 1.8.3.1 @ PATH • 34 ms
[2018-12-03 17:57:12:608] [1] GitService.initialize completed • 574 ms
[2018-12-03 17:57:12:611] Starting repository search in 2 folders
[2018-12-03 17:57:12:611] Searching for repositories (depth=1) in '/home/sistemas/<username>/git/intranet2' ...
[2018-12-03 17:57:12:620] [2] GitService.getRepoPath — e=Uri(file:///home/sistemas/<username>/git/intranet2/js/rrhh/hp/scheduler.js)
[2018-12-03 17:57:12:620] [3] GitService.getRepository — e=Uri(file:///home/sistemas/<username>/git/intranet2/js/rrhh/hp/scheduler.js), t={"skipCacheUpdate":true}
[2018-12-03 17:57:12:629] ShowMessage(error, 'GitLens requires a newer version of Git (>= 2.2.0) than is currently installed (1.8.3.1). Please install a more recent version of Git.', suppressGitVersionWarning, [object Object])
[2018-12-03 17:57:12:629] ShowMessage(error, 'GitLens requires a newer version of Git (>= 2.2.0) than is currently installed (1.8.3.1). Please install a more recent version of Git.', suppressGitVersionWarning, [object Object]) skipped
[2018-12-03 17:57:12:630] GitLens(v9.0.1) activated • 657 ms
[2018-12-03 17:57:12:677] [/home/sistemas/<username>/git/intranet2] git rev-parse --show-toplevel • 65 ms
[2018-12-03 17:57:12:678] Repository found in '/home/sistemas/<username>/git/intranet2'
[2018-12-03 17:57:13:036] Completed repository search (depth=1) in '/home/sistemas/<username>/git/intranet2' • 424 ms
[2018-12-03 17:57:13:037] Searching for repositories (depth=1) in '/home/sistemas/<username>/git/intranet' ...
[2018-12-03 17:57:13:100] [4] GitService.getRepoPath — e=Uri(file:///home/sistemas/<username>/git/intranet2/application/models/deposito/archivo/caja.php)
[2018-12-03 17:57:13:100] [5] GitService.getRepository — e=Uri(file:///home/sistemas/<username>/git/intranet2/application/models/deposito/archivo/caja.php), t={"skipCacheUpdate":true}
[2018-12-03 17:57:13:101] [/home/sistemas/<username>/git/intranet] git rev-parse --show-toplevel • 64 ms
[2018-12-03 17:57:13:102] Repository found in '/home/sistemas/<username>/git/intranet'
[2018-12-03 17:57:13:178] Completed repository search (depth=1) in '/home/sistemas/<username>/git/intranet' • 141 ms
[2018-12-03 17:57:13:208] [/home/sistemas/<username>/git/intranet2] git remote -v • 15 ms
[2018-12-03 17:57:13:386] [/home/sistemas/<username>/git/intranet2] git ls-files -- js/rrhh/hp/scheduler.js • 20 ms
[2018-12-03 17:57:13:386] [6] GitService.isTracked true • 20 ms — e=/home/sistemas/<username>/git/intranet2/js/rrhh/hp/scheduler.js, t=/home/sistemas/<username>/git/intranet2, i={"skipCacheUpdate":true}
[2018-12-03 17:57:13:386] [3] GitService.getRepository completed • 765 ms
[2018-12-03 17:57:13:386] [2] GitService.getRepoPath completed • 766 ms
[2018-12-03 17:57:13:386] [8] GitService.getRepository — e=GitUri(file:///home/sistemas/<username>/git/intranet2/js/rrhh/hp/scheduler.js repoPath=/home/sistemas/<username>/git/intranet2)
[2018-12-03 17:57:13:387] [8] GitService.getRepository completed • 0 ms
[2018-12-03 17:57:13:401] [/home/sistemas/<username>/git/intranet2] git ls-files -- application/models/deposito/archivo/caja.php • 26 ms
[2018-12-03 17:57:13:401] [7] GitService.isTracked true • 26 ms — e=/home/sistemas/<username>/git/intranet2/application/models/deposito/archivo/caja.php, t=/home/sistemas/<username>/git/intranet2, i={"skipCacheUpdate":true}
[2018-12-03 17:57:13:401] [5] GitService.getRepository completed • 301 ms
[2018-12-03 17:57:13:401] [4] GitService.getRepoPath completed • 301 ms
[2018-12-03 17:57:13:401] [a] GitService.getRepository — e=GitUri(file:///home/sistemas/<username>/git/intranet2/application/models/deposito/archivo/caja.php repoPath=/home/sistemas/<username>/git/intranet2)
[2018-12-03 17:57:13:401] [a] GitService.getRepository completed • 0 ms
[2018-12-03 17:57:13:413] [/home/sistemas/<username>/git/intranet2] git ls-files -- /home/sistemas/<username>/git/intranet2/js/rrhh/hp/scheduler.js • 26 ms
[2018-12-03 17:57:13:414] [9] GitService.isTracked true • 26 ms — e=GitUri(file:///home/sistemas/<username>/git/intranet2/js/rrhh/hp/scheduler.js repoPath=/home/sistemas/<username>/git/intranet2)
[2018-12-03 17:57:13:414] [c] GitService.getBlameForLine — e=GitUri(file:///home/sistemas/<username>/git/intranet2/js/rrhh/hp/scheduler.js repoPath=/home/sistemas/<username>/git/intranet2), t=2937
[2018-12-03 17:57:13:414] [d] GitService.getBlameForFile — e=GitUri(file:///home/sistemas/<username>/git/intranet2/js/rrhh/hp/scheduler.js repoPath=/home/sistemas/<username>/git/intranet2)
[2018-12-03 17:57:13:415] [e] GitService.getBlameForFile — e=GitUri(file:///home/sistemas/<username>/git/intranet2/js/rrhh/hp/scheduler.js repoPath=/home/sistemas/<username>/git/intranet2)
[2018-12-03 17:57:13:416] [d] GitService.getBlameForFile Cache miss: 'blame'
[2018-12-03 17:57:13:416] [d] GitService.getBlameForFile Cache add: 'blame'
[2018-12-03 17:57:13:416] [e] GitService.getBlameForFile Cache hit: 'blame'
[2018-12-03 17:57:13:416] [f] GitService.isTracked true • 0 ms — e=GitUri(file:///home/sistemas/<username>/git/intranet2/js/rrhh/hp/scheduler.js repoPath=/home/sistemas/<username>/git/intranet2)
[2018-12-03 17:57:13:440] [/home/sistemas/<username>/git/intranet2] git ls-files -- /home/sistemas/<username>/git/intranet2/application/models/deposito/archivo/caja.php • 38 ms
[2018-12-03 17:57:13:441] [b] GitService.isTracked true • 38 ms — e=GitUri(file:///home/sistemas/<username>/git/intranet2/application/models/deposito/archivo/caja.php repoPath=/home/sistemas/<username>/git/intranet2)
[2018-12-03 17:57:13:441] [10] GitService.getBlameForFile — e=GitUri(file:///home/sistemas/<username>/git/intranet2/application/models/deposito/archivo/caja.php repoPath=/home/sistemas/<username>/git/intranet2)
[2018-12-03 17:57:13:441] [10] GitService.getBlameForFile Cache miss: 'blame'
[2018-12-03 17:57:13:441] [10] GitService.getBlameForFile Cache add: 'blame'
[2018-12-03 17:57:13:441] [11] GitService.isTracked true • 0 ms — e=GitUri(file:///home/sistemas/<username>/git/intranet2/application/models/deposito/archivo/caja.php repoPath=/home/sistemas/<username>/git/intranet2)
[2018-12-03 17:57:13:658] [/home/sistemas/<username>/git/intranet2] git blame --root --incremental -- application/models/deposito/archivo/caja.php • 216 ms
[2018-12-03 17:57:13:658] [12] GitService.getCurrentUser — e=/home/sistemas/<username>/git/intranet2
[2018-12-03 17:57:13:701] [/home/sistemas/<username>/git/intranet2] git config --get-regex user.(name|email) • 42 ms
[2018-12-03 17:57:13:719] git — -c, core.quotepath=false, -c, color.ui=false, check-mailmap, <name> <<username>@domain>, cwd='/home/sistemas/<username>/git/intranet2'
Error: git: 'check-mailmap' is not a git command. See 'git --help'.
[2018-12-03 17:57:13:719] [/home/sistemas/<username>/git/intranet2] git check-mailmap <name> <<username>@domain> • 17 ms
[2018-12-03 17:57:13:719] [12] GitService.getCurrentUser — failed • 60 ms
Error: git: 'check-mailmap' is not a git command. See 'git --help'.
[2018-12-03 17:57:13:719] [10] GitService.getBlameForFile Cache replace (with empty promise): 'blame'
[2018-12-03 17:57:13:719] [10] GitService.getBlameForFile completed • 278 ms
[2018-12-03 17:57:13:975] [/home/sistemas/<username>/git/intranet2] git blame --root --incremental -- js/rrhh/hp/scheduler.js • 557 ms
[2018-12-03 17:57:13:975] [13] GitService.getCurrentUser — e=/home/sistemas/<username>/git/intranet2
[2018-12-03 17:57:13:988] [/home/sistemas/<username>/git/intranet2] git config --get-regex user.(name|email) • 13 ms
[2018-12-03 17:57:14:008] git — -c, core.quotepath=false, -c, color.ui=false, check-mailmap, <name> <<username>@domain>, cwd='/home/sistemas/<username>/git/intranet2'
Error: git: 'check-mailmap' is not a git command. See 'git --help'.
[2018-12-03 17:57:14:008] [/home/sistemas/<username>/git/intranet2] git check-mailmap <name> <<username>@domain> • 19 ms
[2018-12-03 17:57:14:008] [13] GitService.getCurrentUser — failed • 33 ms
Error: git: 'check-mailmap' is not a git command. See 'git --help'.
[2018-12-03 17:57:14:008] [d] GitService.getBlameForFile Cache replace (with empty promise): 'blame'
[2018-12-03 17:57:14:008] [14] GitService.isTracked true • 0 ms — e=GitUri(file:///home/sistemas/<username>/git/intranet2/js/rrhh/hp/scheduler.js repoPath=/home/sistemas/<username>/git/intranet2)
[2018-12-03 17:57:14:009] [d] GitService.getBlameForFile completed • 593 ms
[2018-12-03 17:57:14:009] [e] GitService.getBlameForFile completed • 593 ms
[2018-12-03 17:57:14:009] [c] GitService.getBlameForLine completed • 594 ms
[2018-12-03 17:57:54:593] [15] GitService.getRepository — e=GitUri(untitled:Untitled-1)
[2018-12-03 17:57:54:593] [15] GitService.getRepository completed • 0 ms
[2018-12-03 17:57:54:593] [16] GitService.isTracked false • 0 ms — e=GitUri(untitled:Untitled-1)
I've noticed missing history/blame info since the latest release, and in my case it was related to submodules - main repo stuff was working ok, but there was no info for files in submodules.
Do you use submodules? I will submit a separate issue if these are not related
SirIntruder
on 3 Dec 2018
I'm having the same issue.
GitLens Version: 9.0.1
VSCode Version: 1.29.1
OS Version: macOS 10.14.1
Cannot see gutter blame or blame inline
Something to do with GitService.isTracked false perhaps?
I cannot figure out how to enable this, so it says all my files are not tracked
I do have a submodule and the submodule is not being tracked while the primary repo is.
[2018-12-04 00:13:01:779] [1] GitService.initialize
[2018-12-04 00:13:02:453] Git found: 2.19.0 @ /usr/local/bin/git • 113 ms
[2018-12-04 00:13:02:453] [1] GitService.initialize completed • 674 ms
[2018-12-04 00:13:02:457] Starting repository search in 1 folders
[2018-12-04 00:13:02:462] Searching for repositories (depth=1) in '/Users/michael/projects/migration/access-one.angular-webtop' ...
[2018-12-04 00:13:02:474] [2] GitService.getRepoPath
[2018-12-04 00:13:02:475] [3] GitService.getRepository
[2018-12-04 00:13:02:492] GitLens(v9.0.1) activated • 784 ms
[2018-12-04 00:13:02:528] [/Users/michael/projects/migration/access-one.angular-webtop] git rev-parse --show-toplevel • 64 ms
[2018-12-04 00:13:02:528] Repository found in '/Users/michael/projects/migration/access-one.angular-webtop'
[2018-12-04 00:13:02:617] Completed repository search (depth=1) in '/Users/michael/projects/migration/access-one.angular-webtop' • 154 ms
[2018-12-04 00:13:02:641] [/Users/michael/projects/migration/access-one.angular-webtop] git remote -v • 20 ms
[2018-12-04 00:13:02:644] [3] GitService.getRepository completed • 169 ms
[2018-12-04 00:13:02:658] [/Users/michael/Library/Application Support/Code/User] git rev-parse --show-toplevel • 13 ms
[2018-12-04 00:13:02:658] [2] GitService.getRepoPath completed • 183 ms
[2018-12-04 00:13:02:659] [4] GitService.getRepository
[2018-12-04 00:13:02:659] [4] GitService.getRepository completed • 0 ms
[2018-12-04 00:13:02:675] [] git ls-files -- /Users/michael/Library/Application Support/Code/User/settings.json • 13 ms
[2018-12-04 00:13:02:675] [5] GitService.isTracked false • 16 ms
[2018-12-04 00:13:03:034] [6] GitService.getRepoPath
[2018-12-04 00:13:03:034] [7] GitService.getRepository
[2018-12-04 00:13:03:080] [/Users/michael/projects/migration/access-one.angular-webtop] git ls-files -- src/app/shared/user/user.service.ts • 45 ms
[2018-12-04 00:13:03:080] [8] GitService.isTracked false • 45 ms
[2018-12-04 00:13:03:080] [7] GitService.getRepository completed • 45 ms
[2018-12-04 00:13:03:096] [/Users/michael/projects/migration/access-one.angular-webtop/src/app/shared/user] git rev-parse --show-toplevel • 15 ms
[2018-12-04 00:13:03:096] [6] GitService.getRepoPath Repository found in '/Users/michael/projects/migration/access-one.angular-webtop'
[2018-12-04 00:13:03:097] [6] GitService.getRepoPath completed • 63 ms
[2018-12-04 00:13:03:098] [9] GitService.getRepository
[2018-12-04 00:13:03:098] [9] GitService.getRepository completed • 0 ms
[2018-12-04 00:13:03:122] [/Users/michael/projects/migration/access-one.angular-webtop] git ls-files -- /Users/michael/projects/migration/access-one.angular-webtop/src/app/shared/user/user.service.ts • 24 ms
[2018-12-04 00:13:03:123] [a] GitService.isTracked false • 24 ms
[2018-12-04 00:13:03:247] [/Users/michael/projects/migration/access-one.angular-webtop] git remote -v • 19 ms
[2018-12-04 00:15:03:423] [b] GitService.isTracked false • 0 ms
[2018-12-04 00:15:11:010] [c] GitService.isTracked false • 0 ms
[2018-12-04 00:15:27:313] [d] GitService.getRepoPath
michael-letcher
on 4 Dec 2018
@michael-letcher so normal repos are working but submodules are busted?
eamodio
on 4 Dec 2018
@eamodio Yes, this is when I've opened just the folder.
Note: I do the workaround for working with multiple monitors and opening the folder in a workspace, but Gitlens works... I see my submodule and it works as intended. (Not sure if this is relevant)
michael-letcher
on 4 Dec 2018
In my case, I just have the main repo (no submodules).
tianbis
on 4 Dec 2018
In my root project it is working fine, but it is not working in my packages that are inside the vendor folder (I have a laravel project).
carvemerson
on 4 Dec 2018
Really sorry for the issues and I will be getting a new release out (likely tonight or tomorrow) with a fix. Again sorry for the regression.
eamodio
on 4 Dec 2018
Thanks! now it works gracefully!
carvemerson
on 5 Dec 2018
Still not working for me :( I tried the new update, reinstalled gitlens and restarted code several times. I can't turn on blame inline and the "GitLens: Toggle File Blame Annotations" command doesn't show up.
I'm not using submodules, just a normal repo.
tianbis
on 5 Dec 2018
I just tried the version 8.5.6 (installed manually) and it worked correctly.
tianbis
on 5 Dec 2018
@eltian sorry for conflating your original issue with the submodule issue. They are completely different and looks like your issue is because of your mentioned older git version.
Since I've co-opted this issue, I've opened a new one here #576
eamodio
on 5 Dec 2018
@eamodio Awesome work mate! No issues here for me.
michael-letcher
on 5 Dec 2018
Is the solution to downgrade your git lens version? I'm running one:
vscode: 1.30.1
gitlens: 9.2.2
OS: 10.14.2 (Mojave)
parejadan
on 20 Dec 2018
@parejadan Solution for what? What issue are you having?
eamodio
on 20 Dec 2018
@eamodio non of the gitlens features were responsive and my search results lead me to enable verbose mode. I would then get the GitService.isTracked false output nonstop.
Somehow I was able to get the gitlens to function again by updating my mac's git version among other things (can't remember what old version I was on).
parejadan
on 20 Dec 2018
Ah, I see. I've have quite a few reports of things not working after upgrading to Mojave -- seemingly to do with missing xcode command line tools (or something like that). Is everything working properly now?
eamodio
on 20 Dec 2018
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
![github-actions[bot] picture](https://avatars2.githubusercontent.com/in/15368?v=4&s=40)
github-actions[bot]
on 2 Dec 2020
Related issues
eamodio
·
3Comments
mindpivot
·
4Comments
dwlsalmeida
·
3Comments
derrickstolee
·
3Comments
DFelten
·
3Comments
Most helpful comment
@eltian sorry for conflating your original issue with the submodule issue. They are completely different and looks like your issue is because of your mentioned older git version.
Since I've co-opted this issue, I've opened a new one here #576