Page MenuHomePhabricator

Add a `bin/conduit call` support binary
ClosedPublic

Authored by epriestley on Feb 4 2018, 2:01 PM.
Tags
None
Referenced Files
Unknown Object (File)
Thu, Mar 21, 8:49 AM
Unknown Object (File)
Feb 12 2024, 6:21 PM
Unknown Object (File)
Feb 11 2024, 9:15 AM
Unknown Object (File)
Jan 15 2024, 2:23 PM
Unknown Object (File)
Dec 27 2023, 12:41 PM
Unknown Object (File)
Dec 21 2023, 11:12 PM
Unknown Object (File)
Dec 20 2023, 11:01 AM
Unknown Object (File)
Dec 17 2023, 11:44 AM
Subscribers
None

Details

Summary

Ref T13060. See PHI343. Triaging this bug required figuring out where in the pipeline UTF8 was being dropped, and bisecting the pipeline required making calls to Conduit.

Currently, there's no easy way to debug/inspect arbitrary Conduit calls, especially when they are diffusion.* calls which route to a different host (even if you have a real session and use the web console for these, you just see an HTTP service call to the target host in DarkConsole).

Add a bin/conduit utility to make this kind of debugging easier, with an eye toward the Phacility production cluster (or other similar clusters) specifically.

Test Plan
  • Ran echo '{}' | bin/conduit call --method conduit.ping --input - and similar.
  • Used a similar approach to successfully diagnose the UTF8 issue in T13060.

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable