Skip to content

Fix lock issue causing problems in unmounting repository#193

Merged
jamill merged 2 commits intomicrosoft:milestones/M139from
jamill:lock_fix_to_M139
Aug 21, 2018
Merged

Fix lock issue causing problems in unmounting repository#193
jamill merged 2 commits intomicrosoft:milestones/M139from
jamill:lock_fix_to_M139

Conversation

@jamill
Copy link
Member

@jamill jamill commented Aug 20, 2018

This fixes the main issue that was leading to functional test failures when unmounting repositories.

Due to an bug in the locking logic, the background git status scan (run to rebuild the GitStatusCache), could be denied the GVFS lock, but the command would still be run. This hit other problems later in the command, eventually crashing the GVFS Mount process.

(port pull request #157)

jamill added 2 commits August 20, 2018 17:13
Tweak the order that components are shutdown, to shutdown the
GitStatusCache before other components that it depends on. This is to
prevent problems that might arise from a component being disabled that
GitStatusCache depends on.

(cherry picked from commit 0c09ed4)
This fixes a bug in TryAcquireGVFSLockForProcess where it does not
correctly report whether it was able to acquire the GVFS lock. In
cases where this method retries to acquire the lock, it would report
success, even if it was not able to acquire the lock.

This could lead to problems where commands that depended on the GVFS
could run, even if it did not actually have the lock.

(cherry picked from commit dfbe657)
@jamill jamill merged commit 24bda02 into microsoft:milestones/M139 Aug 21, 2018
@jrbriggs jrbriggs added this to the M139 milestone Aug 21, 2018
@jamill jamill deleted the lock_fix_to_M139 branch April 3, 2019 02:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants