Page MenuHomePhabricator

In "phutil_passthru()", "resolve()" the future rather than calling "execute()" directly
ClosedPublic

Authored by epriestley on Sep 18 2020, 6:22 PM.
Tags
None
Referenced Files
F18808963: D21470.id.diff
Sun, Oct 19, 10:05 AM
F18753589: D21470.id.diff
Sat, Oct 4, 7:33 PM
F18748769: D21470.diff
Sat, Oct 4, 12:34 AM
F18744869: D21470.id51103.diff
Fri, Oct 3, 4:25 AM
F18701501: D21470.id51103.diff
Sep 27 2025, 7:29 PM
F18657299: D21470.diff
Sep 23 2025, 1:16 AM
F18626592: D21470.diff
Sep 16 2025, 1:37 AM
F18220925: D21470.diff
Aug 19 2025, 4:38 PM
Subscribers
None

Details

Summary

See PHI1862. This code calls "execute()" on the future directly, but that skips some steps -- notably, ServiceProfiler hooks.

Call "resolve()", which has the same effect but includes desirable/expected side effects.

Test Plan

Changed a workflow to run "phutil_passthru('ls')", ran it with "--trace". Before: no execution in trace; after: execution in trace.

Diff Detail

Repository
rARC Arcanist
Lint
Lint Not Applicable
Unit
Tests Not Applicable