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
Unknown Object (File)
Mon, Jun 30, 11:54 PM
Unknown Object (File)
Mon, Jun 30, 11:26 AM
Unknown Object (File)
Sat, Jun 28, 6:26 PM
Unknown Object (File)
May 8 2025, 3:06 AM
Unknown Object (File)
Apr 22 2025, 8:07 PM
Unknown Object (File)
Apr 1 2025, 10:40 PM
Unknown Object (File)
Apr 1 2025, 12:57 PM
Unknown Object (File)
Mar 31 2025, 12:04 PM
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
Branch
conduit1
Lint
Lint Passed
Unit
Tests Passed
Build Status
Buildable 24103
Build 33186: Run Core Tests
Build 33185: arc lint + arc unit

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.