[Bug]: Source control UI is unresponsive starting from version 4.10+ #6153
Copy link
Copy link
Closed
Labels
bugSomething isn't workingSomething isn't workingtriageThis issue needs to be triaged by a maintainerThis issue needs to be triaged by a maintainer
Description
Is there an existing issue for this?
- I have searched the existing issues
OS/Web Information
- Web Browser: Chrome
- Local OS: Windows
- Remote OS: Debian
- Remote Architecture: amd64
code-server --version: 4.11.0
Steps to Reproduce
- install code-server 4.11.0 using install shell script
- run code-server
- modify file
- enter source control and try to add file as "git add" through the UI, it is unresponsive. It's not only git add, but also revert and the whole UI for pull/push except git commit
Expected
git functionality as git add / git revert / git pull / git push should happen
Actual
UI is clickable but unresponsive and there are no logs showing in git terminal
Logs
No response
Screenshot/Video
No response
Does this issue happen in VS Code or GitHub Codespaces?
- I cannot reproduce this in VS Code.
- I cannot reproduce this in GitHub Codespaces.
Are you accessing code-server over HTTPS?
- I am using HTTPS.
Notes
This does not happen in 4.9.1 version of the code-server, it started with version 4.10
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't workingtriageThis issue needs to be triaged by a maintainerThis issue needs to be triaged by a maintainer
Activity
code-asher commentedon May 1, 2023
I experimented with the 4.11.0 and 4.12.0 Docker images but had no luck reproducing. Does it only happen with a specific repository and if so is it something that can be shared?
waschinski commentedon May 9, 2023
Same error here, running code-server on a Synology NAS. I noticed every time I click on some Git action like revert or adding a change, "extensions are being activated" is displayed but nothing happens. I have found no errors in the logs.
Can also confirm reverting to 4.9.1 it's working again.
Maybe it has to do with the extension host?
maxorlovsky commentedon May 9, 2023
No it's not public unfortunately and can't be shared. I don't think it's something related to a project I tried with multiple projects.
code-asher commentedon May 9, 2023
maxorlovsky commentedon May 9, 2023
No, command line is unaffected. I can easily do git pull / git commit / git push.
Git log have nothing unfortunately. Is there some kind of verbose command that can be use to output more logs?
code-asher commentedon May 9, 2023
I think if code-server is launched with
--log debug(or--log trace) that will propagate to extensions but I am not sure.code-asher commentedon May 9, 2023
Oh interesting, looks like there is a log level setting for git specifically as well (configured through the settings panel in code-server or through the json file).
code-asher commentedon May 9, 2023
Wild guess, I wonder if it is trying to prompt for credentials but unable to show the popup for whatever reason. Except why would this affect revert or add? So maybe not.
code-asher commentedon May 9, 2023
Another wild guess, are you seeing issues with memory consumption? Saw an issue once where running
git gcresolved a freeze when source control was used.Edit: although, if the problem does not manifest in < 4.10 then probably unrelated.
Anshuldubey0602 commentedon Oct 10, 2023
Same issue with version 4.7.1
bilogic commentedon Nov 3, 2023
Is it only the
Source Controlthat is affected?I was on
4.13.0for a long time, all good, but recently upgraded to4.17.1and4.18.0and running into a similar issue where loading ofSource Controland extensions do not complete.The clocks stay there forever,
Source Controlloading is incomplete and will never complete + there is noActivating extensions ...at the status bar. The way I would describe it isExtensions crashed without errorscode-asher commentedon Nov 16, 2023
@bilogic I have seen a similar issue with #3061 but I am not sure it is the same thing.
bilogic commentedon Nov 16, 2023
@code-asher thanks I think they are the same problem, and this thread has a more accurate description of the problem
bilogic commentedon Nov 20, 2023
More observations:
Source Controlbecomes brokenThis leads me to think that perhaps something in the "Trust workspace" code is broken?
Delete local storage patch
Delete local storage patch
bilogic commentedon Nov 28, 2023
This appears to have been fixed by
4.19.1-rc.2.Ever since upgrading from
4.13.0, I faced the issue about 50% of the time when I open another workspace.I have been swapping workspaces > 20 times on
4.19.1-rc.2and not faced it once,code-asher commentedon Nov 29, 2023
Thank you for confirming! 4.19.1 is now out.
Delete local storage patch