search

gitkraken / vscode-gitlens

Supercharge Git inside VS Code and unlock untapped knowledge within each repository — Visualize code authorship at a glance via Git blame annotations and CodeLens, seamlessly navigate and explore Git repositories, gain valuable insights via rich visualizations and powerful comparison commands, and so much more
http://gitkraken.com/gitlens
Other
8.97k stars 1.3k forks source link

Git blame not visualizing properly #1057

Closed lejean2000 closed 4 years ago

lejean2000 commented 4 years ago

Issue Type: Potential Bug

No visualization of blame anywhere can be seen anywhere (gutter, on the line, heatmap, etc.) All options in the settings are enabled of course, and no zen mode.

This has been reported before, I think, but as a folder name capitalization issue, which is not the problem now. As you can see in the screenshot and the output log, the file is properly tracked and git log issued successfully, and line history to the left is populated correctly.

I have very few extensions running - Python, MagicPython, and Live Share.

Extension version: 10.2.2 VS Code version: Code - Insiders 1.47.0-insider (b16b467d3e03e1a1ae05b5836e4e5a5af504e86d, 2020-07-01T05:32:07.483Z) OS version: Windows_NT x64 10.0.18363

System Info |Item|Value| |---|---| |CPUs|Intel(R) Core(TM) i5-6300HQ CPU @ 2.30GHz (4 x 2304)| |GPU Status|2d_canvas: enabled
flash_3d: enabled
flash_stage3d: enabled
flash_stage3d_baseline: enabled
gpu_compositing: enabled
multiple_raster_threads: enabled_on
oop_rasterization: disabled_off
protected_video_decode: unavailable_off
rasterization: enabled
skia_renderer: disabled_off_ok
video_decode: enabled
viz_display_compositor: enabled_on
viz_hit_test_surface_layer: disabled_off_ok
webgl: enabled
webgl2: enabled| |Load (avg)|undefined| |Memory (System)|15.89GB (7.39GB free)| |Process Argv|| |Screen Reader|no| |VM|31%|

image

lejean2000 commented 4 years ago

This issue was caused by a wrong configuration. Some nonsense passed to gitlens.advanced.blame.customArguments

github-actions[bot] commented 3 years ago

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.