Page MenuHomePhabricator

Provide a "--local" flag to "bin/conduit call" to force in-process execution
ClosedPublic

Authored by epriestley on Apr 14 2020, 7:51 PM.
Tags
None
Referenced Files
F19469060: D21114.id.diff
Sun, Jan 4, 3:10 PM
F19467811: D21114.diff
Sat, Jan 3, 5:52 PM
F19020244: D21114.diff
Nov 23 2025, 5:17 PM
F18844653: D21114.id.diff
Oct 29 2025, 6:57 AM
F18824373: D21114.id.diff
Oct 23 2025, 3:23 PM
F18817920: D21114.diff
Oct 21 2025, 7:28 PM
F18807143: D21114.diff
Oct 18 2025, 11:26 PM
F18773139: D21114.id50285.diff
Oct 9 2025, 7:31 AM
Subscribers
None

Details

Summary

See PHI1692. Currently, it's hard to get a local profile or "--trace" of some Diffusion API methods, since they always proxy via HTTP -- even if the local node can serve the request.

This always-proxy behavior is intentional (so we always go down the same code path, to limit surprises) but inconvenient when debugging. Allow an operator to connect to a node which can serve a request and issue a --local call to force in-process execution.

This makes it straightforward to "--trace" or "--xprofile" the call.

Test Plan

Ran bin/conduit call ... with and without --local using a Diffusion method on a clustered repository. Without --local, saw proxy via HTTP. With --local, saw in-process execution.

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

This revision was not accepted when it landed; it landed in state Needs Review.Apr 14 2020, 8:24 PM
This revision was automatically updated to reflect the committed changes.