-
Notifications
You must be signed in to change notification settings - Fork 27.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Regularly stuck with "Scanning folder for git repositories…" when using Codespaces and VS Code #190024
Comments
@deepak1556 it looks like #178748 has resurfaced. |
Very likely candidate microsoft/vscode-linux-build-agent@a2d892c, will investigate tomorrow. |
Steps for verification:
|
I've checked in the latest Insiders release and the same bug seems to still be present when using GitHub Codespaces (both in web version of VS Code insiders, and desktop version of VS Code insiders when connecting to the Codespace) Version: 1.83.0-insider (Universal) |
the alpine servers run fine with the provided container configuration, however the git scm is hanging for a different reason @lszomoru can you please look into it |
@deepak1556, I have created a new Codespace on the linked repository and I am still able to reproduce the problem. As far as I can tell the extension how is completely busted as running "Show Running Extensions" is empty. In the Window output log I see the following:
If I look at the Git extension I see the following: |
Ah missed the logs, |
Does this issue occur when all extensions are disabled?: N/A (remote extensions are needed)
Steps to Reproduce:
I have seen this issues before months back, and it was fixed in Insiders and subsequently the release version - but it is back again and very frustrating.
I have a minimal repo here https://github.com/jonsage/vscode-git-scanning-bug - you will need to create a Codespace to see the issue (or choose a different devcontainer workflow).
The issue could be to do with the docker image used, I think last time there was some suggestion of a problem with Alpine (or Alpine containers), and I believe the Jekyll container is based on Alpine. too.
The text was updated successfully, but these errors were encountered: