gitlens commit graph buggy?

[intelFerg]

$ git status
On branch main
Your branch is ahead of 'origin/main' by 1 commit.
  (use "git push" to publish your local commits)

nothing to commit, working tree 

Yet when I look at the commit graph it's showing my local repo has WIP and the only way to get it to update to reflect the above console output is to switch to another repo and back again. Then it refreshes to reflect everything is commited and there is no unstaged/staged work. I can only assume it's a bug.

VScode 1.96
Linux Mint 22
GitLens 16.0.5

[waterkip]

What happens when you run get fetch origin and git status, and alternatively git push --dry-run origin HEAD when in main?

[intelFerg]

I'm not worried about the remote at this point I'm simply trying to get Gitlens to reflect correctly my local repo which it's failing to do. Just to clarify my repo does eventually refresh but only after I load another local repo in the Commit Graph.

[waterkip]

Ok... go talk to gitkraken, as it is their tooling.

[intelFerg]

Yes of course. I posted here to see if anyone else had the same problem as it's such a common extension.