Page MenuHomePhabricator

When updating revisions in response to commits, reuse previously generated diffs
ClosedPublic

Authored by epriestley on Jan 9 2017, 7:45 PM.
Tags
None
Referenced Files
F18870284: D17164.id.diff
Tue, Nov 4, 4:25 PM
F18867077: D17164.diff
Mon, Nov 3, 9:23 PM
F18858121: D17164.id41276.diff
Nov 1 2025, 8:49 PM
F18834245: D17164.id41278.diff
Oct 26 2025, 7:26 AM
F18832004: D17164.id41278.diff
Oct 25 2025, 6:08 PM
F18828315: D17164.diff
Oct 24 2025, 3:44 PM
F18749083: D17164.id.diff
Oct 4 2025, 2:21 AM
F18622186: D17164.diff
Sep 15 2025, 10:45 AM
Subscribers
None

Details

Summary

Fixes T10968. In rare situations, we can generate a diff, then hit an error which causes this update to fail.

When it does, we tend to get stuck in a loop creating diffs, which can fill the database up with garbage. We saw this once in the Phacility cluster, and one instance hit it, too.

Instead: when we create a diff, keep track of which commit we generated it from. The next time through, reuse it if we already built it.

Test Plan
  • Used bin/differential attach-commit <commit> <revision> to hit this code.
  • Simulated a filesystem write failure, saw the diff get reused.
  • Also did a normal update, which worked properly.

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable