New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Command execution timeout control #539

bitprophet opened this Issue Jun 19, 2018 · 0 comments


None yet
1 participant

bitprophet commented Jun 19, 2018

Fabric 1 had a feature which (IIRC) used a threading Timer to raise an exception (which I think then just turned into ye olde crappy abort()) when a command execution took longer than the user desired.

This should live at the Invoke layer for v2, even if Fabric's Runner subclass needs hooks to implement it (though I suspect it may not, as long as we interrupt the remote process correctly when we time out - something that may or may not be necessary locally, I'm not positive.)

@bitprophet bitprophet added this to the 1.3 milestone Jun 28, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment