Page MenuHomePhabricator

Don't try to synchronize repositories with no working copy
ClosedPublic

Authored by epriestley on Apr 22 2016, 12:41 PM.
Tags
None
Referenced Files
Unknown Object (File)
Sat, Aug 13, 5:56 PM
Unknown Object (File)
Mon, Aug 8, 6:31 AM
Unknown Object (File)
Mon, Aug 1, 5:57 AM
Unknown Object (File)
Jul 9 2022, 9:32 AM
Unknown Object (File)
Jul 9 2022, 9:32 AM
Unknown Object (File)
Jul 9 2022, 8:00 AM
Unknown Object (File)
Jul 9 2022, 8:00 AM
Unknown Object (File)
Jun 24 2022, 10:46 AM
Subscribers
None

Details

Summary

Ref T4292. Sometimes, we may not have a working copy for a repository. The easiest way to get into this condition is to deactivate a repository.

We could try to clone + fetch in this case, but that's kind of complex, and there's an easy command that administrators can run manually. For now, just tell them to do that.

This affects the inactive repositories on secure, like rGITCOINS.

Test Plan

Removed working copy, got message.

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

epriestley retitled this revision from to Don't try to synchronize repositories with no working copy.
epriestley updated this object.
epriestley edited the test plan for this revision. (Show Details)
epriestley added a reviewer: chad.
chad edited edge metadata.
This revision is now accepted and ready to land.Apr 22 2016, 2:34 PM
This revision was automatically updated to reflect the committed changes.