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
Unknown Object (File)
Oct 22 2024, 9:32 AM
Unknown Object (File)
Oct 21 2024, 7:06 AM
Unknown Object (File)
Oct 14 2024, 1:17 PM
Unknown Object (File)
Oct 2 2024, 3:14 AM
Unknown Object (File)
Sep 7 2024, 9:50 PM
Unknown Object (File)
Sep 6 2024, 8:33 AM
Unknown Object (File)
Sep 6 2024, 8:33 AM
Unknown Object (File)
Sep 6 2024, 8:33 AM
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