epriestley 563dc2a993 In ConduitCallFuture, only call Conduit exception messages on Conduit exceptions ... 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. Maniphest Tasks: T13582 Differential Revision: https://secure.phabricator.com/D21467		2020-09-17 13:20:24 -07:00
..
__tests__	Fully merge "libphutil/" into "arcanist/"	2020-02-12 15:17:38 -08:00
ArcanistConduitCallFuture.php	In ConduitCallFuture, only call Conduit exception messages on Conduit exceptions	2020-09-17 13:20:24 -07:00
ArcanistConduitEngine.php	Implement Conduit login prompt behavior as a pure FutureProxy, not a Future-like object	2020-07-01 06:37:31 -07:00
ArcanistConduitException.php	Collapse Arcanist toolsets from "wilds" into "master", as an overlay layer	2020-02-13 14:10:46 -08:00
ArcanistNoURIConduitException.php	Collapse Arcanist toolsets from "wilds" into "master", as an overlay layer	2020-02-13 14:10:46 -08:00
ConduitClient.php	If the Conduit server asserts it has the "gzip" capability, compress requests	2020-04-14 16:50:54 -07:00
ConduitClientException.php	Fully merge "libphutil/" into "arcanist/"	2020-02-12 15:17:38 -08:00
ConduitFuture.php	When raising a Conduit client exception, show the called method in the error message	2020-09-15 17:34:22 -07:00
ConduitSearchFuture.php	Implement Conduit login prompt behavior as a pure FutureProxy, not a Future-like object	2020-07-01 06:37:31 -07:00
FutureAgent.php	Clean up some service profiler behavior in Conduit futures	2020-07-01 06:37:31 -07:00