-
Notifications
You must be signed in to change notification settings - Fork 28
Add new stop queue action #3054
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
Conversation
b265db0 to
ebf2f74
Compare
719b6e0 to
b18e2ee
Compare
julieg18
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great work!
| }, | ||
| { | ||
| "command": "dvc.stopExperimentsQueue", | ||
| "when": "dvc.commands.available && dvc.project.available" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The stop queue command is always available even when the queue isn't running. Would we want the command to only be available when the queue is running?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We would need to interrogate dvc queue status to know whether or not there is anything running as the information is not readily available from exp show (queue can be started outside of VS Code, e.g in a terminal). It is essentially a no-op when the queue is not running. For now, this is good enough.
|
Code Climate has analyzed commit bb95168 and detected 0 issues on this pull request. The test coverage on the diff in this pull request is 100.0% (85% is the threshold). This pull request will bring the total coverage in the repository to 96.4% (0.0% change). View more on Code Climate. |
1/2
main<- this <- #3059Demo
Screen.Recording.2023-01-06.at.2.33.29.pm.mov