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

Too many changes warning is too persistent and in the wrong place #211096

Closed
alexr00 opened this issue Apr 23, 2024 · 9 comments · Fixed by #211219 or #211328
Closed

Too many changes warning is too persistent and in the wrong place #211096

alexr00 opened this issue Apr 23, 2024 · 9 comments · Fixed by #211219 or #211328
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug git GIT issues insiders-released Patch has been released in VS Code Insiders regression Something that used to work is now broken verified Verification succeeded
Milestone

Comments

@alexr00
Copy link
Member

alexr00 commented Apr 23, 2024

image

I checked-out an old commit from 7 years ago (a8c629d). The SCM view got stuck displaying the "busy" badge and showed many file changes, along with a warning about too many changes.

When I changed views, the warning stuck around even on top of other view containers. Eventually, it moved into the top right corner. The SCM view now appears to be permanently busy.

@lszomoru
Copy link
Member

That does not look good. I am also able to reproduce in Stable so I believe that this was broken last milestone.
It's very easy to reproduce by setting git.statusLimit to 3 and then making changes to 4 files.

@lszomoru lszomoru added bug Issue identified by VS Code Team member as probable bug git GIT issues labels Apr 23, 2024
@lszomoru lszomoru added this to the April 2024 milestone Apr 23, 2024
@lszomoru
Copy link
Member

Adding @benibenj and @TylerLeonhardt to see if this rings a bell for them as the made changes to IContextViewService recently. Based on my tests, this worked fine in 1.87 but it's broken with 1.88. I stepped through the SCM code and it seems that no changes in execution there.

@TylerLeonhardt
Copy link
Member

I didn't do any crazy changes there AFAIK, I feel like @benibenj was maybe more in there so could you take a look first?

benibenj added a commit that referenced this issue Apr 24, 2024
@benibenj benibenj added the regression Something that used to work is now broken label Apr 24, 2024
@benibenj
Copy link
Contributor

Found the culprit #207520. Fix it with #211219

benibenj added a commit that referenced this issue Apr 24, 2024
@justschen justschen added the unreleased Patch has not yet been released in VS Code Insiders label Apr 24, 2024
@benibenj benibenj reopened this Apr 24, 2024
@vscodenpa vscodenpa removed the unreleased Patch has not yet been released in VS Code Insiders label Apr 24, 2024
@benibenj
Copy link
Contributor

It turns out the fix actually breaks hovers entirely. @TylerLeonhardt you turned the disposable into a MutableDisposable which I believe does not work in this context. I think we should revert 09d9b06.

@TylerLeonhardt
Copy link
Member

@benibenj I can drive reverting that commit but think this should be revisited in debt week as we have disposables there not getting disposed of.

@lszomoru
Copy link
Member

Thank you @benibenj and @TylerLeonhardt.

benibenj added a commit that referenced this issue Apr 25, 2024
@benibenj
Copy link
Contributor

@TylerLeonhardt I had a closer look at the code. The concept of using disposables for this case was flawed from the start. I created a fix for it.

benibenj added a commit that referenced this issue Apr 25, 2024
@vscodenpa vscodenpa added the unreleased Patch has not yet been released in VS Code Insiders label Apr 25, 2024
@TylerLeonhardt
Copy link
Member

Thanks for doing that @benibenj!

@vscodenpa vscodenpa added insiders-released Patch has been released in VS Code Insiders and removed unreleased Patch has not yet been released in VS Code Insiders labels Apr 25, 2024
@alexr00 alexr00 added the verified Verification succeeded label Apr 26, 2024
@microsoft microsoft locked and limited conversation to collaborators Jun 9, 2024
nang-dev pushed a commit to trypear/pearai-app that referenced this issue Oct 3, 2024
nang-dev pushed a commit to trypear/pearai-app that referenced this issue Oct 3, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue identified by VS Code Team member as probable bug git GIT issues insiders-released Patch has been released in VS Code Insiders regression Something that used to work is now broken verified Verification succeeded
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants