Change:
Type: <bBug</bI simply switched to a branch, perhaps with a rather long name. On this branch, the source control tree doesn't open and remains in a collapsed state. VS Code version: Code 1.85.1 (, 2023-12-13T09:49:37.021Z) OS version: WindowsNT x64 10.0. Modes: <details<summarySystem Info</summary </details<details<summaryExtensions (26)</summaryExtensionVersion ------ vscode-nginx-conf0.3.2 path-intellisense2.8.5 vscode-markdownlint0.53.0 vscode-eslint2.4.2 gitlens14.6.1 EditorConfig0.16.4 prettier-vscode10.1.0 vscode-nginx-conf-hint0.3.0 react-component1.1.0 svg1.5.3 vscode-styled-components1.7.0 vscode-docker1.28.0 csdevkit1.1.16 csharp2.14.8 vscode-dotnet-runtime2.0.0 vscodeintellicode-csharp0.1.26 vscode-kubernetes-tools1.3.15 remote-containers0.327.0 remote-wsl0.81.8 powershell2023.8.0 nginx-formatter0.0.13 vscode-yaml1.14.0 vscode-nginx0.6.0 vscode-asciidoc0.0.3 vscode-styled-components1.7.8 vscode-nginx0.7.2 (1 theme extensions excluded) </details<details<summaryA/B Experiments</summary</details<!-- generated by issue reporter --
are you able to reproduce the issue with the latest VS Code Insiders release?
It can still be reproduced withe latest VS Code Insiders Release. I attach a film. My branch name: bugfix-CAR-5045-loading-compositions-component-order-messed-up-when-selecting-lumped-from !
thanks for the recording. Could you also please share the contents of the git output window which you can access by invoking the "Git: Show Git Output" command from the command palette. Thanks! Also, can you still reproduce the issue if you set the following settings to : scm.showIncomingChanges scm.showOutgoingChanges
2024-01-08 11:34:18.008 [info] fatal: failed to stat 'refs/heads/bugfix-CAR-5045-loading-compositions-component-order-messed-up-when-selecting-lumped-': Filename too long
what version of VS Code are you using? Are you using the latest VS Code Insiders release?
Version: 1.86.0-insider (user setup) Commit: Date: 2024-01-08T05:36:56.355Z Electron: 27.1.3 ElectronBuildId: Chromium: 118.0.5993.159 18.17.1 V8: 11.8.172.18-electron.0 OS: Windows_NT x64 10.0.
are you saying that you are still able to reproduce this issue with the latest VS Code Insiders release? Thanks!
Duplicate of

Discussion:
} async getCommitCount(range: string): Promise<{ ahead: number; behind: number }> { <del> const result = await this.exec(['rev-list', '--count', '--left-right', range]); </del> <ins> const args = ['rev-list', '--count', '--left-right', range]; if (isWindows) { args.splice(0, 0, '-c', 'core.longpaths=true'); } const result = await this.exec(args); </ins> const [ahead, behind] = result.stdout.trim().split('t'); return { ahead: Number(ahead) || 0, behind: Number(behind) || 0 };

return undefined; } <del> const commitCount = await this.repository.getCommitCount(`${refId1}...${refId2}`); return { id: ancestor, ahead: commitCount.ahead, behind: commitCount.behind }; </del> <ins> try { const commitCount = await this.repository.getCommitCount(`${refId1}...${refId2}`); return { id: ancestor, ahead: commitCount.ahead, behind: commitCount.behind }; } catch (err) { this.logger.error(`Failed to get ahead/behind for '${refId1}...${refId2}': ${err.message}`); } return undefined; </ins> } provideFileDecoration(uri: Uri): FileDecoration | undefined {