Vscode-gitlens: Git lens current line blame not working in the new VS Code insiders Version

Created on 14 Feb 2019 · 10Comments · Source: eamodio/vscode-gitlens

Issue Type: Bug

Git lense current line blame not showing up !

Extension version: 9.5.1
VS Code version: Code - Insiders 1.32.0-insider (a509265116babc17648c9052eeeb8ae2909fed87, 2019-02-13T06:14:01.838Z)
OS version: Linux x64 4.15.0-43-generic

System Info

|Item|Value|
|---|---|
|CPUs|Intel(R) Core(TM) i7-7700 CPU @ 3.60GHz (8 x 4094)|
|GPU Status|2d_canvas: enabled
checker_imaging: disabled_off
flash_3d: enabled
flash_stage3d: enabled
flash_stage3d_baseline: enabled
gpu_compositing: enabled
multiple_raster_threads: enabled_on
native_gpu_memory_buffers: disabled_software
rasterization: disabled_software
surface_synchronization: enabled_on
video_decode: unavailable_off
webgl: enabled
webgl2: enabled|
|Load (avg)|2, 2, 2|
|Memory (System)|15.55GB (1.20GB free)|
|Process Argv|.|
|Screen Reader|no|
|VM|0%|

needs more info

Source

prasanthnv

Most helpful comment

Strangely enough, just setting the outputLevel to debug fixed the issue for me. Switched back to errors and everything still worked.

metra on 21 Feb 2019

👍2 😄1

All 10 comments

@prasanthnv Hrm, I'm not seeing any issue in the latest insiders. Can you try re-installing GitLens? If you are still having an issue, 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 15 Feb 2019

Strangely enough, just setting the outputLevel to debug fixed the issue for me. Switched back to errors and everything still worked.

metra on 21 Feb 2019

👍2 😄1

I still can't enable current line blame annotations on VSCode 1.31.1:

Version: 1.31.1
Commit: 1b8e8302e405050205e69b59abb3559592bb9e60
Date: 2019-02-12T02:20:54.427Z
Electron: 3.1.2
Chrome: 66.0.3359.181
Node.js: 10.2.0
V8: 6.6.346.32
OS: Windows_NT x64 10.0.17763

Guria on 27 Feb 2019

Just found out that in my case it conflicting with another extension:

Name: Render CRLF
Id: medo64.render-crlf
Description: Displays LF/CR/CRLF line ending (aka end-of-line, EOL) symbols when Render whitespace is turned on.
Version: 1.3.0
Publisher: Josip Medved
VS Marketplace Link: https://marketplace.visualstudio.com/items?itemName=medo64.render-crlf

Guria on 27 Feb 2019

👍1

@Guria Ah, glad you found the issue and that it is resolved.

I'm going to close this issue for now, until there is more information pointing to an issue. Thanks!

eamodio on 9 Mar 2019

Just in case it helps anyone... in my case :man_facepalming: the file I was looking at was git-crypted. The blame works fine for a plain text file.

gservat on 20 Mar 2019

This bug is still reproducible. I have opened it with VSCode repo as I feel it is more relevant there. Recording it here since it affects both gitlens and vscode's gutters at the same time.

No extensions except gitlens were installed.

rohansekhri on 13 Feb 2020

@rohansekhri Could you be running into: microsoft/vscode#12448? Are you using 10.2.1?

eamodio on 23 Mar 2020

@eamodio My bug is a subset of this one. The real cause is actually the case-(in)sensitivity of VSCode. Please ignore my comments above. It is not a GitLens issue. By the way, if you are interested in logs for GitLens to do any enhancements, I have posted them in my bug. Thanks

rohansekhri on 23 Mar 2020

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.