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

Window activity API - window becomes inactive during long running git operation #211064

Closed
lszomoru opened this issue Apr 23, 2024 · 3 comments · Fixed by #214264
Closed

Window activity API - window becomes inactive during long running git operation #211064

lszomoru opened this issue Apr 23, 2024 · 3 comments · Fixed by #214264
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug insiders-released Patch has been released in VS Code Insiders
Milestone

Comments

@lszomoru
Copy link
Member

lszomoru commented Apr 23, 2024

Testing #210978

  • Add a git pre-commit hook that sleeps for 120 seconds
  • Make a change to a file, and commit the change
  • Switch to another VS Code window

Expected behaviour:

  • Window should be active while the source control operation running

Actual behaviour:

  • Window becomes inactive even though the source control operation is still running
@connor4312
Copy link
Member

Can this be adopted in SCM? Holding an activity lock is fairly easy, just call this method 🙂

/**
* Marks the user as being active until the Disposable is disposed of.
* Multiple consumers call this method; the user will only be considered
* inactive once all consumers have disposed of their Disposables.
*/
markActive(): IDisposable;

@lszomoru
Copy link
Member Author

@connor4312, these commands are being contributed by the git extension. Should markActive() be wired into the IProgressService so that in case there is an on-going progress indicator the window is considered active?

@lszomoru lszomoru added the under-discussion Issue is under discussion for relevance, priority, approach label May 27, 2024
@connor4312
Copy link
Member

Yea, I think that's reasonable, thanks for the suggestion. Will take care of it 🙂

@connor4312 connor4312 added bug Issue identified by VS Code Team member as probable bug and removed under-discussion Issue is under discussion for relevance, priority, approach labels May 28, 2024
@VSCodeTriageBot VSCodeTriageBot added the unreleased Patch has not yet been released in VS Code Insiders label Jun 5, 2024
@VSCodeTriageBot VSCodeTriageBot added this to the June 2024 milestone Jun 5, 2024
@VSCodeTriageBot VSCodeTriageBot 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 Jun 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Issue identified by VS Code Team member as probable bug insiders-released Patch has been released in VS Code Insiders
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants