Add `--[no-]remote-execution` flag #7991
We want to allow users to permanently configure all remoting options in their
Instead, users should be able to turn on remoting at the per-invocation level, just like we have
Users can have all their remoting config setup and still be able to entirely run locally. Also now more explicit when you are and are not remoting.
referenced this pull request
Jul 1, 2019
illicitonion left a comment
This works for me, but it may be worth thinking about whether this is really a boolean, or will be an enum in the future? In particular, when speculation is a thing, will we want:
That approach sounds great to me! Default to
Though, this assumes that there are instances where users would only want to remote and not speculate? Do we anticipate that being the case?
Closely related, in Slack Stu mentioned the option for the speculate timeout threshold. I think that is should be separate from this option here, but this is one possible way of doing this:
There was some discussion of this in slack (here), and my takeaway was that if remoting is enabled, we should have a good set of defaults for that case which will include speculation (by default). So I leaned toward the boolean flag.
Agreed. If you have remoting, by default it makes sense to have speculation also enabled.
So long as we have some mechanism to turn off speculation, which we can do via something like