Page MenuHomePhabricator

Make repository daemons periodically check for out-of-sync repositories
ClosedPublic

Authored by epriestley on Jan 31 2019, 8:19 PM.
Tags
None
Referenced Files
F19496605: D20078.diff
Jan 8 2026, 11:45 AM
F19102669: D20078.id47948.diff
Dec 5 2025, 7:19 AM
F19093227: D20078.id.diff
Dec 3 2025, 8:54 PM
F19086266: D20078.id47948.diff
Dec 2 2025, 8:58 PM
F19082552: D20078.diff
Dec 2 2025, 11:32 AM
F18853941: D20078.id.diff
Oct 31 2025, 8:45 PM
F18849673: D20078.diff
Oct 30 2025, 11:20 AM
F18819206: D20078.id47948.diff
Oct 22 2025, 5:00 AM
Subscribers
None

Details

Summary

See PHI1015. If you add new repository nodes to a cluster, we may not actually sync some repositories for up to 6 hours (if they've had no commits for 30 days).

Add an explicit check for out-of-sync repositories to trigger background sync.

Test Plan
  • Ran bin/phd debug pullocal.
  • Fiddled with the repository_workingcopy version table to put the local node in and out of sync with the cluster.
  • Saw appropriate responses in the daemon (sync; wait if the last sync trigger was too recent).

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

src/applications/repository/management/PhabricatorRepositoryManagementWorkflow.php
10

This is a fix for PHP 7.3+ complaining about count(null) when you run bin/repository update with no arguments.

This revision is now accepted and ready to land.Feb 1 2019, 4:27 AM
This revision was automatically updated to reflect the committed changes.