Page MenuHomePhabricator

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

Authored by epriestley on Feb 26 2020, 4:39 PM.
Tags
None
Referenced Files
F18734168: D21031.id.diff
Tue, Sep 30, 10:49 PM
F18657104: D21031.id50138.diff
Tue, Sep 23, 12:31 AM
F18629494: D21031.diff
Tue, Sep 16, 9:05 AM
F18599302: D21031.diff
Sat, Sep 13, 7:08 AM
F18567677: D21031.id.diff
Sep 9 2025, 4:04 PM
F18459372: D21031.id50100.diff
Sep 1 2025, 4:51 PM
F18376759: D21031.diff
Aug 28 2025, 11:44 AM
F18142049: D21031.id50138.diff
Aug 14 2025, 11:31 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