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
F14758239: D21388.diff
Wed, Jan 22, 5:54 AM
Unknown Object (File)
Tue, Jan 21, 10:07 AM
Unknown Object (File)
Fri, Jan 17, 6:34 PM
Unknown Object (File)
Sun, Jan 12, 9:47 PM
Unknown Object (File)
Wed, Jan 1, 12:06 AM
Unknown Object (File)
Tue, Dec 31, 7:38 PM
Unknown Object (File)
Wed, Dec 25, 2:46 AM
Unknown Object (File)
Dec 14 2024, 3:57 PM
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.