Page MenuHomePhabricator

Make updating a revision with the same active diff a no-op
ClosedPublic

Authored by epriestley on Mar 29 2018, 4:54 PM.
Tags
None
Referenced Files
F22794697: D19267.id46122.diff
Wed, Oct 7, 12:59 AM
F22663313: D19267.diff
Thu, Oct 1, 11:15 AM
F22632292: D19267.id46123.diff
Wed, Sep 30, 2:05 AM
F22621007: D19267.id.diff
Tue, Sep 29, 4:10 PM
F22597267: D19267.diff
Mon, Sep 28, 1:39 PM
Unknown Object (File)
Sep 2 2026, 9:31 PM
Unknown Object (File)
Sep 2 2026, 2:08 PM
Unknown Object (File)
Aug 22 2026, 1:42 AM
Subscribers
None

Details

Summary

Ref T13114. See PHI515. Updating a revision with the same, currently active diff became an error at some point (probably D19175). This is inconsistent; make it an allowable no-op instead.

Test Plan
  • Updated a revision's diff via Conduit.
  • Updated to the same diff, no-op.
  • Tried to update a different revision, error ("already attached elsewhere").
  • Updated with a different diff.
  • Tried to update with the original diff, error ("previously attached version").

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable