You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Should commands be allowed to run for an unlimited amount of time? If so, we can close this. Otherwise we need to keep track of how long a command has been running for and cancel it after some timeout. We can test with the following command:
This issue has been marked stale because it has been open for 60 days with no activity. If there is no activity within 7 days, it will be closed.
This is an automation to keep issues manageable and actionable and is not a comment on the quality of this issue nor on the work done so far. Closed issues are still valuable to the project and are available to be searched.
Should commands be allowed to run for an unlimited amount of time? If so, we can close this. Otherwise we need to keep track of how long a command has been running for and cancel it after some timeout. We can test with the following command:
We probably want any timeout to be pretty long, but actually letting things run forever is sub-optimal.
Related: #361
The text was updated successfully, but these errors were encountered: