Page MenuHomePhabricator

In ConduitCallFuture, only call Conduit exception messages on Conduit exceptions
ClosedPublic

Authored by epriestley on Sep 17 2020, 8:19 PM.
Tags
None
Referenced Files
F15406691: D21467.diff
Tue, Mar 18, 1:22 PM
F15379533: D21467.diff
Thu, Mar 13, 9:42 PM
F15302815: D21467.id51097.diff
Wed, Mar 5, 10:20 PM
F15297103: D21467.id.diff
Wed, Mar 5, 11:57 AM
F15285618: D21467.id51096.diff
Tue, Mar 4, 2:49 PM
Unknown Object (File)
Mon, Mar 3, 3:43 PM
Unknown Object (File)
Fri, Feb 21, 2:57 PM
Unknown Object (File)
Wed, Feb 19, 9:22 PM
Subscribers
None

Details

Summary

Ref T13582. When this code is reached with a raw HTTP exception, it currently fatals.

Test Plan
  • Ran arc branches --conduit-uri=http://example.org (a bad Conduit URI).
  • Before: hard fatal with a bad method call.
  • After: non-Conduit exception raised to user. Not ideal, but a step forward.

Diff Detail

Repository
rARC Arcanist
Lint
Lint Not Applicable
Unit
Tests Not Applicable