Page MenuHomePhabricator

For changesets that affect binaries, use the new binary file content hash as an effect hash
ClosedPublic

Authored by epriestley on Apr 27 2020, 3:29 PM.
Tags
None
Referenced Files
F18762942: D21174.diff
Mon, Oct 6, 9:41 PM
F18761431: D21174.id50421.diff
Mon, Oct 6, 2:19 PM
F18761278: D21174.id.diff
Mon, Oct 6, 1:22 PM
F18761273: D21174.id50422.diff
Mon, Oct 6, 1:20 PM
F18736372: D21174.id50422.diff
Wed, Oct 1, 5:38 AM
F18672894: D21174.diff
Thu, Sep 25, 8:34 AM
F18645708: D21174.diff
Fri, Sep 19, 8:26 AM
F18636316: D21174.id.diff
Wed, Sep 17, 3:56 AM
Subscribers
None

Details

Summary

Ref T13522. When changesets update an image, we currently compute no effect hash. A content hash of the image (or other binary file) is a reasonable effect hash, and enalbes effect-hash-based behavior, including hiding files in intradiffs.

Test Plan
  • Created a revision affecting cat.png and quack.txt (currently, there must be 2+ changesets to trigger the hide logic).
  • Updated it with the exact same changes.
  • Viewed revision:
    • Saw the image renderered in the interdiff.
  • Applied patch.
  • Ran bin/differential rebuild-changesets ....
  • Viewed revision:
    • Saw both changesets collapse as unchanged.

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable