Page MenuHomePhabricator

Remove the "timeout" parameter from "Future->resolve()"
ClosedPublic

Authored by epriestley on Feb 26 2020, 4:39 PM.
Tags
None
Referenced Files
F18790654: D21031.id.diff
Wed, Oct 15, 4:21 PM
F18783736: D21031.id50138.diff
Mon, Oct 13, 9:11 AM
F18783732: D21031.id50100.diff
Mon, Oct 13, 9:10 AM
F18781893: D21031.diff
Sun, Oct 12, 11:59 PM
F18734168: D21031.id.diff
Sep 30 2025, 10:49 PM
F18657104: D21031.id50138.diff
Sep 23 2025, 12:31 AM
F18629494: D21031.diff
Sep 16 2025, 9:05 AM
F18599302: D21031.diff
Sep 13 2025, 7:08 AM
Subscribers
None

Details

Summary

Ref T11968. This future-level parameter has no nontrivial callers and makes the "fate of FutureGraph" changes more difficult.

Callers that are genuinely interested in this behavior can wrap the Future in a FutureIterator and use "setUpdateInterval()" to get the same behavior.

Test Plan

Grepped for "resolve()" and "resolvex()", updated callers.

Diff Detail

Repository
rARC Arcanist
Lint
Lint Not Applicable
Unit
Tests Not Applicable