Current line blame no showing

[masics]

The "current line blame" is not showing anymore.

• GitLens Version:
  Extension version: 10.2.0
  VS Code version: Code 1.41.1 (26076a4de974ead31f97692a0d32f90d735645c0, 2019-12-18T14:58:56.166Z)
  OS version: Windows_NT x64 10.0.18363
  Remote OS version: Linux x64 4.4.0-18362-Microsoft
  Remote OS version: Linux x64 4.4.0-18362-Microsoft

Debug after changing line with a mouse:

[2020-01-27 03:25:18:171] [6b] LineAnnotationController.onActiveLinesChanged — e=editor=file:///c:/projects/myfile.txt, lines=undefined, pending=true, reason=selection
[2020-01-27 03:25:18:171] [6c] LineAnnotationController.clear completed • 0 ms
[2020-01-27 03:25:18:171] [6b] LineAnnotationController.onActiveLinesChanged completed • 0 ms
[2020-01-27 03:25:18:171] [6d] LineHoverController.onActiveLinesChanged — e=editor=file:///c:/projects/myfile.txt, lines=undefined, pending=true, reason=selection
[2020-01-27 03:25:18:171] [6d] LineHoverController.onActiveLinesChanged completed • 0 ms
[2020-01-27 03:25:18:171] [6e] StatusBarController.onActiveLinesChanged — e=editor=file:///c:/projects/myfile.txt, lines=undefined, pending=true, reason=selection
[2020-01-27 03:25:18:171] [6e] StatusBarController.onActiveLinesChanged completed • 0 ms
[2020-01-27 03:25:18:422] [6f] LineAnnotationController.onActiveLinesChanged — e=editor=file:///c:/projects/myfile.txt, lines=undefined, pending=false, reason=selection
[2020-01-27 03:25:18:422] [70] LineAnnotationController.clear completed • 0 ms
[2020-01-27 03:25:18:422] [6f] LineAnnotationController.onActiveLinesChanged completed • 0 ms
[2020-01-27 03:25:18:422] [71] LineHoverController.onActiveLinesChanged — e=editor=file:///c:/projects/myfile.txt, lines=undefined, pending=false, reason=selection
[2020-01-27 03:25:18:422] [71] LineHoverController.onActiveLinesChanged completed • 0 ms
[2020-01-27 03:25:18:422] [72] StatusBarController.onActiveLinesChanged — e=editor=file:///c:/projects/myfile.txt, lines=undefined, pending=false, reason=selection
[2020-01-27 03:25:18:423] [72] StatusBarController.onActiveLinesChanged completed • 0 ms

[waracci]

Same case for macOs Mohave Version 10.14.5.

VsCode Version: 1.41.1
Commit: 26076a4de974ead31f97692a0d32f90d735645c0

Git lens version 10.2.0

[konradsa]

Same here after upgrading to VSCode 1.42. Checked the settings and tried the toggle, but nto shown anymore.

[eamodio]

What version of Git are you all using? Any chance 10.2.1 fixes the issue?

[masics]

What version of Git are you all using? Any chance 10.2.1 fixes the issue?

2.25.0.windows.1

[eamodio]

@masics Thanks -- Git 2.25 definitely caused a bunch of issues with GitLens. Can you try 10.2.1 and see if it fixes things?

[masics]

@masics Thanks -- Git 2.25 definitely caused a bunch of issues with GitLens. Can you try 10.2.1 and see if it fixes things?

Are there any chances you will adopt 2.25+?

[eamodio]

As long as Git doesn't have another breaking change it should be fine (2.25 was the first time I've had to deal with Git breaking things)

[masics]

As long as Git doesn't have another breaking change it should be fine (2.25 was the first time I've had to deal with Git breaking things)

What exactly it broke?

[Conduitry]

I still had a bunch of broken features with gitlens 10.2.1, git 2.25.0. For now I've downgraded the version of git used by vscode.

[eamodio]

@Conduitry what broken issues have you seen with Git 2.25 and GitLens 10.2.1? If you are still seeing issues, please file them.

[eamodio]

I am closing this issue because it needs more information and has not had recent activity. Please re-open this issue when more details can be provided.

Thanks!

[masics]

I still don't see the blame lines. What extra information do you require?

[eamodio]

@masics Are you using 10.2.1? If so, does the folder you are opening in vscode match the casing of the folder on disk? (VS Code has issues if there is any casing differences because what is on disk and how you open the folder in VS Code -- which then causes GitLens issues).

[masics]

Yes, I'm using 10.2.1 The folder in VSC is shown in all capital letters while on disk it is in lower case. But I'm on Windows - casing is ignored, isn't it? Best regards, Michael Strelnikov

…

On Mon, 23 Mar 2020 at 18:35, Eric Amodio ***@***.***> wrote: @masics <https://github.com/masics> Are you using 10.2.1? If so, does the folder you are opening in vscode match the casing of the folder on disk? (VS Code has issues if there is any casing differences because what is on disk and how you open the folder in VS Code -- which then causes GitLens issues). — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#939 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABSDCBTKUNAB6GNMLYZTOKTRI4GN3ANCNFSM4KL3GO5A> .

[eamodio]

See microsoft/vscode#12448
Also the main issue you are hitting with GitLens is that Git isn't case-insensitive by default. So to fix this, you either need to open the folder in vscode exactly as it is on disk (recommended, as you will likely hit other issues), or change you Git config to ignore case:
https://stackoverflow.com/questions/52950/how-to-make-git-ignore-changes-in-case#53116

Hope that helps.

[masics]

I don't know how to "open a folder with the same case" - I provided the full path as it appears on the file system. But VCS still showing it in capital cases (the hint is still showing in lower case). When I applied "ignore case" for the git I see the blame lines again. But they are much slower than before - it takes time for a line to appear after I change lines.

[github-actions]

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.