-
Notifications
You must be signed in to change notification settings - Fork 154
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
Handle KeyboardInterrupt
in CLI when getting run plan
#1626
Comments
This issue is stale because it has been open for 30 days with no activity. |
I hope this message finds you well. I would like to express my interest in taking on issue #1626, which involves handling the Please assign this issue to me at your earliest convenience @peterschmidt85 . |
@IshuSinghSE Sure, feel free to send your PR! |
Co-authored-by: Ishu Singh <[email protected]>
* Fix Handle KeyboardInterrupt in CLI when getting run plan #1626 * Allow using all existing regions unless a specific set of regions is configured #1573 * Delete src/dstack/_internal/cli/commands/apply.py * Revert "Delete src/dstack/_internal/cli/commands/apply.py" This reverts commit 0e6a938. * Fix use all available runpod regions by default --------- Co-authored-by: Ishu Singh <[email protected]>
Steps to reproduce
dstack apply
a run configurationExpected behavior
dstack apply
exits cleanly.Actual behavior
The text was updated successfully, but these errors were encountered: