No automatic refresh of repositories that are outside of the workspace

[michael-lang]

Steps:
Open the GitLens window
Use the VSCode window footer to change to another branch.
GitLens does not update the checkmark to be on the current branch.
Use the refresh button in Gitlens to update the active branch checkmark.
No change, the wrong branch still has a checkmark. In the prior version of gitlens this workaround worked. Although the workaround itself should not be needed.

Log output:
[2018-12-07 19:03:41:361] [c:/dev/Repos/eisa] git status --porcelain=v2 --branch -u • 2356 ms
[2018-12-07 19:03:41:361] [c:/dev/Repos/eisa] git status --porcelain=v2 --branch -u • 93 ms (await)
[2018-12-07 19:03:41:793] [c:/dev/Repos/eisa] git branch -vv --abbrev=40 -a • 108 ms
[2018-12-07 19:11:56:773] [c:/dev/Repos/eisa] git status --porcelain=v2 --branch -u • 96 ms
[2018-12-07 19:11:56:773] [c:/dev/Repos/eisa] git status --porcelain=v2 --branch -u • 91 ms (await)
[2018-12-07 19:11:58:606] [c:/dev/Repos/eisa] git branch -vv --abbrev=40 -a • 88 ms
[2018-12-07 19:12:04:764] [c:/dev/Repos/eisa] git status --porcelain=v2 --branch -u • 54 ms
[2018-12-07 19:12:12:888] [c:/dev/Repos/eisa] git status --porcelain=v2 --branch -u • 76 ms

Extension version: 9.0.3
VS Code version: Code 1.29.1 (bc24f98b5f70467bc689abf41cc5550ca637088e, 2018-11-15T19:13:36.375Z)
OS version: Windows_NT x64 10.0.17134

System Info

Item	Value
CPUs	Intel(R) Core(TM) i7-7500U CPU @ 2.70GHz (4 x 2904)
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: enabled video_decode: enabled video_encode: enabled webgl: enabled webgl2: enabled
Memory (System)	15.90GB (9.38GB free)
Process Argv
Screen Reader	no
VM	0%

[eamodio]

I can't reproduce this -- when I switch branches via the status bar or command line, GitLens detects it and updates appropriately. Is there anything special about this repo? Does it happen on all repos? Are there any other details you can provide?

[michael-lang]

You're right. I didn't have the problem on another repo. I'll try to find what is unique about the repo.

…

On Fri, Dec 7, 2018, 5:33 PM Eric Amodio ***@***.*** wrote: I can't reproduce this -- when I switch branches via the status bar or command line, GitLens detects it and updates appropriately. Is there anything special about this repo? Does it happen on all repos? Are there any other details you can provide? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#583 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAT5fPiICaFc5H8haQYXUAvq1omci0jUks5u2vregaJpZM4ZI_-Z> .

[michael-lang]

I may have confused the issue. The problem does occur still in both my current repos.

Notice in the screenshot the current branch is correctly reflected at the top. However, under "Branches" the checkmark is still next to the last branch I was working on. Also I just deleted a couple local branches and they are still in the branches list. Gitlens sees no commits in the branch after delete, but it doesnt realize the branch doesn't exist anymore.

Pressing the "Refresh: icon of the "Repositories" panel does not update the branches list. In a prior version of Gitlens the branches did not update automatically, but the Refresh icon did update them.

If the branches list isn't up to date, then the context menu is wrong, which prevents me from merging between branches and following the "gitflow" process.

My current workaround is to close VS code after every branch change so the branches list is up to date. Its not a very good workaround. Isn't the refresh icon supposed to update the branches?

[eamodio]

@michael-lang I just released GitLens 9.2.3 which should fix the refresh issue, but I'm still at a loss to understand the root issue. Can you please reproduce the issue and send me both the steps that show the problem and the logs that go along with those steps?

[viktordd]

Hi I have the same issue.
The picture below shows the state after deleting a local branch, then creating a new branch. The branch list in gitlens is not updating. I have tried to fetch, pull, and refresh on git lens, but the Branches list does not update. You can see on the left it shows I have 2 local branches and 3 on Git Lens.
I have the latest GitLens version 9.2.3

[michael-lang]

We use gitflow, so we have lots of branches (over 100) at origin. I usually only keep 5-10 of them locally. Maybe the number of branches is a contributing factor?

1. open gitlens
2. expand branches list
3. change branches

The current branch name is changed. The branches node still shows the prior branch with a checkmark. the context menu for the prior branch is still the current branch context menu, so I can't merge that prior branch to current.

[eamodio]

@michael-lang So using the refresh button with GitLens 9.2.3 didn't help? Can you provide logs please?

[eamodio]

Also @michael-lang @viktordd can you also verify that this setting isn't set gitlens.views.repositories.autoRefresh to false

[michael-lang]

9.2.3 did not fix the problem I was having. But I did find the cause.

I have a git repo with multi-projects in it. At the root is a visual studio solution, which I edit using Visual Studio 2017. I also have a folder under the root for an Angular 7 project, which I open directly in VS Code. The Git repo root is at the parent folder of what I have open in VS Code.

If I open the full git repo in VSCode, then Gitlens works as expected.

repoRoot\  (open this folder in VS Code and Gitlens works)
   .git\
   .vs\
   Test.ClassLibrary\
   Test.MvcApi\
   test-ng-cli\   (open this folder in VS Code and Gitlens has the issue)

I do this because I don't want to edit C# files and try to run C# MVC APIs from VSCode. But VS Code is great for Angular projects.

[eamodio]

Ah, that explains it and also why the refresh button wasn't working for you even in 9.2.3. This problem is a consequence of this issue: microsoft/vscode#3025

Until that is resolved, I will add an indicator that shows that the repo won't be automatically updated. And will ensure that caching won't be used unless I can detect repository changes.

[eamodio]

@michael-lang @viktordd can you try out this build and see if it resolves the issue for you? Again GitLens still won't be able to detect the repository change (until the vscode issue is fixed), but the refresh button should work properly now. You should also see an indicator in the Repositories view when GitLens won't be able to automatically detect changes.

Please remove the .zip from the end of the file and install the vsix.
gitlens-9.2.4-beta.vsix.zip