unify status #1546
Draft
unify status #1546
Conversation
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
Collaborator
Author
This stack of pull requests is managed by Graphite. Learn more about stacking. |
Mbeaulne
force-pushed
the
12-12-unify_status
branch
from
9f6b924 to
ad3b972
Compare
Mbeaulne
force-pushed
the
12-12-unify_status
branch
from
ad3b972 to
f8a495c
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
Refactored task status handling to use the new
ContainerExecutionStatustype consistently throughout the UI. Added utility functions to derive execution status from stats and to generate user-friendly status labels.Key changes:
executionStatus.tsutility with functions for status handlingTaskNodeto derive status from execution stats rather than using the deprecatedgetRunStatusType of Change
Checklist
Test Instructions