Page MenuHomePhabricator

Call didRejectResult() in DiffusionCommitQuery properly
ClosedPublic

Authored by epriestley on Jun 14 2015, 10:28 PM.
Tags
None
Referenced Files
F13147711: D13289.diff
Fri, May 3, 3:41 PM
F13144877: D13289.diff
Fri, May 3, 8:35 AM
Unknown Object (File)
Thu, Apr 25, 2:27 AM
Unknown Object (File)
Mon, Apr 22, 6:50 PM
Unknown Object (File)
Thu, Apr 11, 9:51 AM
Unknown Object (File)
Tue, Apr 9, 12:04 PM
Unknown Object (File)
Thu, Apr 4, 7:59 PM
Unknown Object (File)
Thu, Apr 4, 3:51 PM
Subscribers

Details

Summary

Ref T4345. This error is per object-type in the query implementations, not a mail/permissions issue.

Without didRejectResult(), we can't distinguish between "restricted" and "unknown" for objects filtered by willFilterPage().

  • Call didRejectResult() on commits.
  • Make didRejectResult() handle both existing policy exceptions and filtering.
  • Recover from partial objects (like commits) which are missing attached data required to figure out policies.
Test Plan

Saw "Restricted Diffusion Commit" instead of "Unknown Object (Diffusion Commit)" when viewing nonvisible commit handle in Maniphest.

Diff Detail

Repository
rP Phabricator
Branch
mail1
Lint
Lint Passed
Unit
Tests Passed
Build Status
Buildable 6758
Build 6780: [Placeholder Plan] Wait for 30 Seconds

Event Timeline

epriestley retitled this revision from to Call didRejectResult() in DiffusionCommitQuery properly.
epriestley updated this object.
epriestley edited the test plan for this revision. (Show Details)
epriestley added reviewers: btrahan, joshuaspence.
This revision is now accepted and ready to land.Jun 14 2015, 10:31 PM
This revision was automatically updated to reflect the committed changes.