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
F13046338: D21284.diff
Thu, Apr 18, 8:56 AM
Unknown Object (File)
Mon, Apr 1, 9:49 PM
Unknown Object (File)
Sun, Mar 31, 7:20 PM
Unknown Object (File)
Fri, Mar 29, 1:59 AM
Unknown Object (File)
Thu, Mar 28, 10:01 PM
Unknown Object (File)
Mar 5 2024, 1:18 PM
Unknown Object (File)
Feb 21 2024, 12:21 PM
Unknown Object (File)
Jan 20 2024, 1:29 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.