Page MenuHomePhabricator

Clean up `catch (ConduitException $ex)` in Diffusion
Closed, ResolvedPublic

Description

For proxied repositories, this may actually be a ConduitClientException. We should make the stack throw a consistent exception, but likely also reduce the reliance of Diffusion on catching these.

Revisions and Commits

Restricted Differential Revision
Restricted Differential Revision

Event Timeline

epriestley raised the priority of this task from to Normal.
epriestley updated the task description. (Show Details)
epriestley added a project: Phacility.
epriestley added a subscriber: epriestley.
epriestley added a revision: Restricted Differential Revision.Feb 3 2015, 2:03 PM
epriestley added a commit: Restricted Diffusion Commit.Feb 3 2015, 5:54 PM
  • I think we should make callConduitWithDiffusionRequest() always throw ConduitClientException (never ConduitException), I guess?
  • But maybe look through callsites and see if they can all be removed like D11646. Since calls have a nontrivial cost now, it's better if we can avoid making calls that will fail. If they can, we could ignore the exception inconsistency.
btrahan added a revision: Restricted Differential Revision.Feb 17 2015, 9:06 PM
btrahan added a commit: Restricted Diffusion Commit.Feb 17 2015, 10:01 PM

D11789 ended up taking care of all of these.