Page MenuHomePhabricator

Clean up some service profiler behavior in Conduit futures
ClosedPublic

Authored by epriestley on Jul 1 2020, 1:24 PM.
Tags
None
Referenced Files
F15457764: D21388.id50913.diff
Sun, Mar 30, 6:36 PM
F15453144: D21388.id.diff
Sat, Mar 29, 9:44 AM
F15451000: D21388.diff
Fri, Mar 28, 7:36 PM
F15375138: D21388.diff
Wed, Mar 12, 9:48 PM
F15335442: D21388.id50913.diff
Sat, Mar 8, 3:25 PM
F15334511: D21388.diff
Sat, Mar 8, 10:05 AM
F15331484: D21388.id.diff
Fri, Mar 7, 10:36 AM
F15311758: D21388.id50904.diff
Thu, Mar 6, 10:45 AM
Subscribers
None

Details

Summary

Correct two minor Conduit future issues:

  • FutureAgent shows up in the trace log as "<mystery>". Since it isn't doing anything useful, solve the mystery and drop it from the log.
  • Simply the ConduitFuture code for interacting with the service profiler now that a more structured integration is available.
Test Plan

Ran "arc branches --trace", saw conduit calls and no more "<mystery>" clutter.

Diff Detail

Repository
rARC Arcanist
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

This revision was not accepted when it landed; it landed in state Needs Review.Jul 1 2020, 1:37 PM
This revision was automatically updated to reflect the committed changes.