Skip to content

RepoRegistry: ignore non-existent repos#1652

Merged
derrickstolee merged 1 commit intomicrosoft:masterfrom
derrickstolee:deleted-repos
Apr 14, 2020
Merged

RepoRegistry: ignore non-existent repos#1652
derrickstolee merged 1 commit intomicrosoft:masterfrom
derrickstolee:deleted-repos

Conversation

@derrickstolee
Copy link
Contributor

@derrickstolee derrickstolee commented Apr 13, 2020

The 'gvfs mount' command will send a message over the named pipe to
deactivate a repo. This marks it with "IsActive = false" so we don't
try to mount it at service startup. However, a repo can be deleted
and then there is no way to send this message again.

Instead, ignore repositories where the enlistment root does not
exist. Don't remove it from the registry, since there may be a
subtle reason why it is not visible from the service (such as a
removed USB drive).

Resolves #1651.

The 'gvfs mount' command will send a message over the named pipe to
deactivate a repo. This marks it with "IsActive = false" so we don't
try to mount it at service startup. However, a repo can be deleted
and then there is no way to send this message again.

Instead, ignore repositories where the enlistment root does not
exist. Don't remove it from the registry, since there may be a
subtle reason why it is not visible from the serivce (such as a
removed USB drive).

Signed-off-by: Derrick Stolee <dstolee@microsoft.com>
@derrickstolee derrickstolee merged commit 729fed1 into microsoft:master Apr 14, 2020
@derrickstolee derrickstolee mentioned this pull request Apr 15, 2020
derrickstolee added a commit that referenced this pull request Apr 15, 2020
Includes the following PRs:

* #1642: Update Git to v2.26.0 
* #1647: Fix commit-graph expiration
* #1652: RepoRegistry: ignore non-existent repos
* #1653: Update Git to include v2.26.1

The update to include Git v2.26.0 comes with a new default backend for `git rebase`. By switching from the `apply` backend to the `merge` backend, some rebase situations that would previously fail will now succeed automatically. This comes with a slight performance drawback, but it is the direction that the Git community has decided to go. Please see [the Git documentation](https://git-scm.com/docs/git-rebase#_behavioral_differences) for more details.
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.

Deleted repo continues to try remounting

2 participants