Git changes and staged files aren't visible in VS Code v1.85

[tasteslikestrawberries]

Does this issue occur when all extensions are disabled?: Yes/No

• VS Code Version: 1.85.0
• OS Version: Windows 11

Steps to Reproduce:

1. Make a change in a file within git repository and save
2. Select Source control -> file that is changed is not visible (list is empty)

Same happens when staging files. Staged files are not visible.

Downgraded to 1.84.2 and the issue is gone. Before downgrading, tried reinstalling VS Code and disabling/reenabling built-in Git extensions - didn't help.

[jacobweberbowery]

Looks like the same issue as #200387

[lszomoru]

/gifPlease

[sedghi]

@lszomoru I put screenshots in the other issue

[Hadatko]

+1

[mrovinsky]

I have the same issue with VSCode 1.85.1
Staging / commiting suddenly stopped working today

[lszomoru]

Thanks for filing the issue. This does seem like a regression but I would need a little bit more information in order to investigate the issue. While adding a "+1" helps with gaging the breadth of the impact it does not help with getting to the bottom of the issue.

Could any of you provide a recording (https://gifcap.dev) of the issue. Also it would help if we could try to narrow things down:

1. Does it happen for all repositories, or just one particular repository,
2. Does it happen for all files in the repository or just some,
3. is there anything specific to the repository/environment,
4. Does pressing the refresh button help?
5. Does the issue get resolved if you set scm.showIncomingChanges and scm.showOutgoingChanges to false?

Thanks!

[sedghi]

1. It does happen for all repositories for me
2. for all files
3. mono repo, it was working before though
4. No it does not

[sivavemulapalli]

This is related to the issue reported here =>#201099

[lszomoru]

Today's VS Code Insider release (version details below) contains a potential fix along with some additional logging. Could you please download it and see if that that resolves the issue? Thanks!

Version: 1.86.0-insider (Universal)
Commit: a017b12b9caa3475675cfe6fda014fcf5af388c9
Date: 2023-12-19T05:38:28.077Z
Electron: 27.1.3
ElectronBuildId: 25612240
Chromium: 118.0.5993.159
Node.js: 18.17.1
V8: 11.8.172.18-electron.0
OS: Darwin arm64 23.1.0

[sedghi]

@lszomoru Hey I was looking at the Iteration Plan for January 2024 and i didn't see this issue being marked as planned there? I'm not sure how your development cycle works, will all the bug fixes in the Insider get included in the next release by defualt?

I see your Triage Bot has marked this is not planned which worries me

[lszomoru]

@sedghi, I have fixed some issues in this area so it would be extremely helpful if any of the contributors on this issue would try out the latest VS Code Insiders release to make sure that the problem has been resolved. Thanks!

[sedghi]

I've been using insiders and it seems to be resolved. If you have any questions or want to know more, feel free to ask and I'll be happy to help.
I'm just not really like the insiders experience, would like the fix to be applied on the stable

[lszomoru]

@sedghi, thanks for getting back to me and for confirming that the issue is resolved in Insiders. The fix will be included in the next Stable release that will be released towards the end of January.