Better status indicators for running jobs.#1130
Merged
Merged
Conversation
Collaborator
|
I really like this, I did some messing around and got the system to do a nice indicator in the annotation-UI on desktop/Web so that while a job is running on the current data it disables the pipeline button and prevents the user from clicking on it to start another pipeline. |
BryonLewis
approved these changes
Jan 24, 2022
Collaborator
BryonLewis
left a comment
BryonLewis
left a comment
There was a problem hiding this comment.
Looks good and I think this truly helps the user understand that jobs are in progress on specific datasets.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Expose and centralize what jobs are running on what datasets.
Now, running jobs are visible directly in the data browser. This will hopefully lead to less confusion about why "Launch annotator' isn't visible during transcoding or what pipelines are running.
Nothing is visible for training yet because training isn't "blocking" anything.