Skip to content
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

Closed
jonsage opened this issue Aug 9, 2023 · 7 comments · Fixed by #191633
Assignees
Labels
*as-designed Described behavior is as designed bug Issue identified by VS Code Team member as probable bug confirmed Issue has been confirmed by VS Code Team member linux Issues with VS Code on Linux regression Something that used to work is now broken remote Remote system operations issues

Comments

@jonsage
Copy link

jonsage commented Aug 9, 2023

Does this issue occur when all extensions are disabled?: N/A (remote extensions are needed)

  • VS Code Version: 1.81.0 (Universal) and 1.82.0-insider (Universal)
  • OS Version: MacOS 13.3.1 (22E261) [Ventura]

Steps to Reproduce:

  1. Open a repository with a devcontainer from GitHub Codespaces (either in browser VS Code, or desktop)
  2. Look at the Source Control tab - it says "Scanning folder for git repositories…"

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.

@lszomoru
Copy link
Member

@deepak1556 it looks like #178748 has resurfaced.
I am able to reproduce with the latest Insiders release.

@deepak1556
Copy link
Contributor

Very likely candidate microsoft/vscode-linux-build-agent@a2d892c, will investigate tomorrow.

@deepak1556 deepak1556 added bug Issue identified by VS Code Team member as probable bug linux Issues with VS Code on Linux remote Remote system operations issues confirmed Issue has been confirmed by VS Code Team member labels Aug 22, 2023
@deepak1556 deepak1556 added this to the August 2023 milestone Aug 22, 2023
@deepak1556 deepak1556 added the regression Something that used to work is now broken label Aug 22, 2023
@deepak1556
Copy link
Contributor

Steps for verification:

@VSCodeTriageBot VSCodeTriageBot added unreleased Patch has not yet been released in VS Code Insiders insiders-released Patch has been released in VS Code Insiders and removed unreleased Patch has not yet been released in VS Code Insiders labels Aug 29, 2023
@dbaeumer dbaeumer added the verified Verification succeeded label Aug 31, 2023
@jonsage
Copy link
Author

jonsage commented Sep 13, 2023

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)
Commit: f36df69
Date: 2023-09-13T05:34:48.836Z
Electron: 25.8.0
ElectronBuildId: 23503258
Chromium: 114.0.5735.289
Node.js: 18.15.0
V8: 11.4.183.29-electron.0
OS: Darwin x64 22.4.0

@deepak1556
Copy link
Contributor

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 deepak1556 reopened this Sep 13, 2023
@deepak1556 deepak1556 removed their assignment Sep 13, 2023
@deepak1556 deepak1556 removed this from the August 2023 milestone Sep 13, 2023
@VSCodeTriageBot VSCodeTriageBot removed the insiders-released Patch has been released in VS Code Insiders label Sep 13, 2023
@deepak1556 deepak1556 removed the verified Verification succeeded label Sep 13, 2023
@lszomoru
Copy link
Member

@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:

2023-09-27 21:42:17.569 [error] [Extension Host] Error: Error relocating /vscode/bin/linux-alpine/8bac42dd1ec2bb223e847a16437b196c040680e5-insider/node_modules/@vscode/spdlog/build/Release/spdlog.node: _ZSt28__throw_bad_array_new_lengthv: symbol not found
    at Module._extensions..node (node:internal/modules/cjs/loader:1338:18)
    at Module.load (node:internal/modules/cjs/loader:1117:32)
    at Module._load (node:internal/modules/cjs/loader:958:12)
    at u._load (/vscode/bin/linux-alpine/8bac42dd1ec2bb223e847a16437b196c040680e5-insider/out/vs/workbench/api/node/extensionHostProcess.js:154:5631)
    at Module.require (node:internal/modules/cjs/loader:1141:19)
    at require (node:internal/modules/cjs/helpers:110:18)
    at bindings (/vscode/bin/linux-alpine/8bac42dd1ec2bb223e847a16437b196c040680e5-insider/node_modules/bindings/bindings.js:112:48)
    at Object.<anonymous> (/vscode/bin/linux-alpine/8bac42dd1ec2bb223e847a16437b196c040680e5-insider/node_modules/@vscode/spdlog/index.js:3:35)
    at Module._compile (node:internal/modules/cjs/loader:1254:14)
    at Module._extensions..js (node:internal/modules/cjs/loader:1308:10)
    at Module.load (node:internal/modules/cjs/loader:1117:32)
    at Module._load (node:internal/modules/cjs/loader:958:12)
    at u._load (/vscode/bin/linux-alpine/8bac42dd1ec2bb223e847a16437b196c040680e5-insider/out/vs/workbench/api/node/extensionHostProcess.js:154:5631)
    at Module.require (node:internal/modules/cjs/loader:1141:19)
    at require (node:internal/modules/cjs/helpers:110:18)
    at i (/vscode/bin/linux-alpine/8bac42dd1ec2bb223e847a16437b196c040680e5-insider/out/vs/loader.js:5:98)
    at n.load (/vscode/bin/linux-alpine/8bac42dd1ec2bb223e847a16437b196c040680e5-insider/out/vs/loader.js:4:1651)
    at _.load (/vscode/bin/linux-alpine/8bac42dd1ec2bb223e847a16437b196c040680e5-insider/out/vs/loader.js:3:9105)
    at u (/vscode/bin/linux-alpine/8bac42dd1ec2bb223e847a16437b196c040680e5-insider/out/vs/loader.js:5:9362)
    at Object.errorback (/vscode/bin/linux-alpine/8bac42dd1ec2bb223e847a16437b196c040680e5-insider/out/vs/loader.js:5:9481)
    at _.triggerErrorback (/vscode/bin/linux-alpine/8bac42dd1ec2bb223e847a16437b196c040680e5-insider/out/vs/loader.js:3:9399)
    at /vscode/bin/linux-alpine/8bac42dd1ec2bb223e847a16437b196c040680e5-insider/out/vs/loader.js:3:9150
    at n.load (/vscode/bin/linux-alpine/8bac42dd1ec2bb223e847a16437b196c040680e5-insider/out/vs/loader.js:4:1668)
    at _.load (/vscode/bin/linux-alpine/8bac42dd1ec2bb223e847a16437b196c040680e5-insider/out/vs/loader.js:3:9105)
    at u (/vscode/bin/linux-alpine/8bac42dd1ec2bb223e847a16437b196c040680e5-insider/out/vs/loader.js:5:9362)
    at h._loadModule (/vscode/bin/linux-alpine/8bac42dd1ec2bb223e847a16437b196c040680e5-insider/out/vs/loader.js:5:9490)
    at h._resolve (/vscode/bin/linux-alpine/8bac42dd1ec2bb223e847a16437b196c040680e5-insider/out/vs/loader.js:6:452)
    at h.defineModule (/vscode/bin/linux-alpine/8bac42dd1ec2bb223e847a16437b196c040680e5-insider/out/vs/loader.js:5:5585)
    at h._relativeRequire (/vscode/bin/linux-alpine/8bac42dd1ec2bb223e847a16437b196c040680e5-insider/out/vs/loader.js:5:6209)
    at e (/vscode/bin/linux-alpine/8bac42dd1ec2bb223e847a16437b196c040680e5-insider/out/vs/loader.js:5:8540)
    at R.S (/vscode/bin/linux-alpine/8bac42dd1ec2bb223e847a16437b196c040680e5-insider/out/vs/workbench/api/node/extensionHostProcess.js:110:18463)
    at new Promise (<anonymous>)
    at R (/vscode/bin/linux-alpine/8bac42dd1ec2bb223e847a16437b196c040680e5-insider/out/vs/workbench/api/node/extensionHostProcess.js:110:18443)
    at k.s (/vscode/bin/linux-alpine/8bac42dd1ec2bb223e847a16437b196c040680e5-insider/out/vs/workbench/api/node/extensionHostProcess.js:110:19558)
    at new k (/vscode/bin/linux-alpine/8bac42dd1ec2bb223e847a16437b196c040680e5-insider/out/vs/workbench/api/node/extensionHostProcess.js:110:19433)
    at L.s (/vscode/bin/linux-alpine/8bac42dd1ec2bb223e847a16437b196c040680e5-insider/out/vs/workbench/api/node/extensionHostProcess.js:135:1780)
    at L.createLogger (/vscode/bin/linux-alpine/8bac42dd1ec2bb223e847a16437b196c040680e5-insider/out/vs/workbench/api/node/extensionHostProcess.js:110:4881)
    at new L (/vscode/bin/linux-alpine/8bac42dd1ec2bb223e847a16437b196c040680e5-insider/out/vs/workbench/api/node/extensionHostProcess.js:118:27160)
    at p.j (/vscode/bin/linux-alpine/8bac42dd1ec2bb223e847a16437b196c040680e5-insider/out/vs/workbench/api/node/extensionHostProcess.js:106:1241)
    at /vscode/bin/linux-alpine/8bac42dd1ec2bb223e847a16437b196c040680e5-insider/out/vs/workbench/api/node/extensionHostProcess.js:106:2914
    at q.a (/vscode/bin/linux-alpine/8bac42dd1ec2bb223e847a16437b196c040680e5-insider/out/vs/workbench/api/node/extensionHostProcess.js:90:21046)
    at get value [as value] (/vscode/bin/linux-alpine/8bac42dd1ec2bb223e847a16437b196c040680e5-insider/out/vs/workbench/api/node/extensionHostProcess.js:90:21194)
    at Object.get (/vscode/bin/linux-alpine/8bac42dd1ec2bb223e847a16437b196c040680e5-insider/out/vs/workbench/api/node/extensionHostProcess.js:106:3304)
    at new o (/vscode/bin/linux-alpine/8bac42dd1ec2bb223e847a16437b196c040680e5-insider/out/vs/workbench/api/node/extensionHostProcess.js:141:1147)
    at i (/vscode/bin/linux-alpine/8bac42dd1ec2bb223e847a16437b196c040680e5-insider/out/vs/workbench/api/node/extensionHostProcess.js:154:9765)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)

If I look at the Git extension I see the following:

Image

@deepak1556
Copy link
Contributor

Ah missed the logs, jekyll/jekyll:4 is based on alpine-3.15 https://github.com/envygeeks/jekyll-docker/blob/fb892998d444b7b2e4074adeb032197f67853c0a/opts.yml#L1 whereas our server alpine modules are built on alpine-3.16. We don't plan to revert the alpine version as 3.15 is reaching EOL https://www.alpinelinux.org/releases/. I am closing this as designed, please update the jekyll container to use >=3.16

@deepak1556 deepak1556 closed this as not planned Won't fix, can't repro, duplicate, stale Sep 28, 2023
@deepak1556 deepak1556 added the *as-designed Described behavior is as designed label Sep 28, 2023
@github-actions github-actions bot locked and limited conversation to collaborators Nov 12, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
*as-designed Described behavior is as designed bug Issue identified by VS Code Team member as probable bug confirmed Issue has been confirmed by VS Code Team member linux Issues with VS Code on Linux regression Something that used to work is now broken remote Remote system operations issues
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants