Page MenuHomePhabricator

Add an "Unreachable" flag for commits and revive them during discovery
ClosedPublic

Authored by epriestley on Jun 16 2016, 2:30 PM.
Tags
None
Referenced Files
Unknown Object (File)
Fri, May 3, 3:42 AM
Unknown Object (File)
Thu, May 2, 1:22 PM
Unknown Object (File)
Wed, May 1, 9:46 AM
Unknown Object (File)
Mon, Apr 29, 3:44 PM
Unknown Object (File)
Wed, Apr 24, 11:42 PM
Unknown Object (File)
Thu, Apr 11, 7:59 AM
Unknown Object (File)
Mon, Apr 8, 1:58 PM
Unknown Object (File)
Mar 16 2024, 2:26 AM
Subscribers
None

Details

Summary

Ref T9028. This is the easy part of dealing with deleted commits:

  • Add a flag for unreachable commits (nothing sets this flag yet).
  • Ignore unreachable commits when querying for known commits during discovery, so we pretend they do not exist.
  • When recording a commit, try just reviving an existing unreachable commit first. If that works, bail out.
Test Plan
  • Artificially marked a commit as unreachable with raw SQL.
  • Verified it said "deleted: unreachable" in the UI.
  • Ran repository discover --trace --verbose.
  • Saw the discovery process ignore the commit when filling the cache.
  • Saw the discovery process revive the commit instead of trying to record it again.
  • Web UI now shows the commit as normal.
  • Running repository discover again doesn't make any further changes.

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

epriestley retitled this revision from to Add an "Unreachable" flag for commits and revive them during discovery.
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.Jun 16 2016, 2:31 PM
This revision was automatically updated to reflect the committed changes.