Page MenuHomePhabricator

When executing a repository passthru command via CommandEngine, don't set a timeout
ClosedPublic

Authored by epriestley on May 22 2020, 12:45 PM.
Tags
None
Referenced Files
F18094537: D21284.id50686.diff
Thu, Aug 7, 10:11 PM
F18082832: D21284.id50682.diff
Tue, Aug 5, 7:36 AM
F18079348: D21284.id.diff
Mon, Aug 4, 9:11 PM
F18047260: D21284.diff
Sun, Aug 3, 11:36 AM
F17844075: D21284.id.diff
Jul 27 2025, 1:38 AM
F17843529: D21284.id.diff
Jul 27 2025, 1:01 AM
F17829256: D21284.id.diff
Jul 26 2025, 9:55 AM
F17827705: D21284.diff
Jul 26 2025, 8:28 AM
Subscribers
None

Details

Summary

Ref T13541. The passthru future does not have time limit behavior, so if we reach this code we currently fail.

Phabricator never reaches this code normally, but this code is reachable during debugging if you try to foreground a slow fetch to inspect it.

Passthru commands generally only make sense to run interactively, and the caller or control script can enforce their own timeouts (usually by pressing "^C" with their fingers).

Test Plan

Used a debugging script to run ref-by-ref fetches in the foreground.

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

This revision was not accepted when it landed; it landed in state Needs Review.May 22 2020, 6:54 PM
This revision was automatically updated to reflect the committed changes.