Skip to content

Conversation

@Mbeaulne
Copy link
Collaborator

@Mbeaulne Mbeaulne commented Dec 18, 2025

Description

Enhanced status visualization with detailed tooltips for pipeline runs. The status bar now shows more granular execution states and provides tooltips with detailed breakdowns of task statuses. This improves visibility into pipeline execution states by displaying the actual execution statuses rather than simplified aggregates.

We’ll display the raw status coming from the server, but map it to a “pretty” label in the UI so we can localize later, if we need to:

const EXECUTION_STATUS_LABELS: Record<string, string> = {
  CANCELLED: "Cancelled",
  CANCELLING: "Cancelling",
  FAILED: "Failed",
  INVALID: "Invalid",
  PENDING: "Pending",
  QUEUED: "Queued",
  RUNNING: "Running",
  SKIPPED: "Skipped",
  SUCCEEDED: "Succeeded",
  SYSTEM_ERROR: "System error",
  UNINITIALIZED: "Uninitialized",
  WAITING: "Waiting",
  WAITING_FOR_UPSTREAM: "Waiting for upstream",
} as const satisfies Record<ContainerExecutionStatus | "WAITING", string>;

Previously we grouped several “pending-like” states together (e.g., PENDING, QUEUED, WAITING, WAITING_FOR_UPSTREAM) and displayed them all as Pending.

Now, each execution state displays its own label and its own status color. Some statuses still share the same color to indicate they’re part of the same general category/type (e.g., multiple “in progress / not started yet” states use yellow).

export const EXECUTION_STATUS_BG_COLORS: Record<string, string> = {
  SUCCEEDED: "bg-green-500",
  FAILED: "bg-red-500",
  SYSTEM_ERROR: "bg-red-700",
  INVALID: "bg-red-600",
  RUNNING: "bg-blue-500",
  PENDING: "bg-yellow-500",
  QUEUED: "bg-yellow-500",
  WAITING_FOR_UPSTREAM: "bg-slate-500",
  SKIPPED: "bg-slate-400",
  CANCELLED: "bg-gray-700",
  CANCELLING: "bg-gray-500",
  UNINITIALIZED: "bg-yellow-400",
  WAITING: "bg-yellow-500",
};

Type of Change

  • Improvement
  • Cleanup/Refactor

Checklist

  • I have tested this does not break current pipelines / runs functionality
  • I have tested the changes on staging

Screenshots (if applicable)

Here is a real example of my local env

Screenshot 2025-12-19 at 1.59.58 PM.png

Here is some test data (ignore the state on the left, I was just feeding fake data into the bar for the screenshots below, so it would contain all states)

Screenshot 2025-12-19 at 1.50.24 PM.png

Screenshot 2025-12-19 at 1.50.35 PM.png

Screenshot 2025-12-19 at 1.51.05 PM.png

Screenshot 2025-12-19 at 1.51.28 PM.png

Screenshot 2025-12-19 at 1.51.38 PM.png

Screenshot 2025-12-19 at 1.53.10 PM.png

states.mov (uploaded via Graphite)

Test Instructions

  1. Run a pipeline with various task statuses
  2. Hover over status bars in the run list and run details page
  3. Verify tooltips show detailed breakdowns of execution statuses
  4. Check that status indicators correctly reflect the current state of tasks

Additional Comments

This change introduces a new utility module for execution status handling and standardizes how we display and aggregate execution statuses throughout the UI.

Copy link
Collaborator Author

Mbeaulne commented Dec 18, 2025

@Mbeaulne Mbeaulne force-pushed the 12-18-unify_status_better branch from a02a1f1 to 3029633 Compare December 18, 2025 20:56
@Mbeaulne Mbeaulne mentioned this pull request Dec 18, 2025
8 tasks
@Mbeaulne Mbeaulne changed the title unify status better Enhance status bar with detailed execution status tooltips Dec 18, 2025
@Mbeaulne Mbeaulne force-pushed the 12-18-unify_status_better branch 8 times, most recently from a2650c8 to 1e3965d Compare December 19, 2025 17:36
@Mbeaulne Mbeaulne changed the title Enhance status bar with detailed execution status tooltips Remove @radix-ui/react-hover-card and improve execution status display Dec 19, 2025
@Mbeaulne Mbeaulne force-pushed the 12-18-unify_status_better branch 5 times, most recently from 7c954c4 to 949efd4 Compare December 19, 2025 18:44
@Mbeaulne Mbeaulne changed the title Remove @radix-ui/react-hover-card and improve execution status display Remove @radix-ui/react-hover-card and refactor execution status handling Dec 19, 2025
@Mbeaulne Mbeaulne force-pushed the 12-18-unify_status_better branch 3 times, most recently from b8a7076 to 227876d Compare December 19, 2025 19:05
@Mbeaulne Mbeaulne marked this pull request as ready for review December 19, 2025 19:06
@Mbeaulne Mbeaulne requested a review from a team as a code owner December 19, 2025 19:06
@Mbeaulne Mbeaulne requested a review from maxy-shpfy December 19, 2025 19:06
"@radix-ui/react-checkbox": "^1.3.3",
"@radix-ui/react-collapsible": "^1.1.3",
"@radix-ui/react-dialog": "^1.1.14",
"@radix-ui/react-hover-card": "^1.1.15",
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

wondering if we can split PRs?

@Mbeaulne Mbeaulne force-pushed the 12-18-unify_status_better branch 2 times, most recently from 589df57 to e1a9094 Compare December 19, 2025 19:38
@Mbeaulne Mbeaulne force-pushed the 12-18-unify_status_better branch from e1a9094 to 65cdf3c Compare December 19, 2025 20:12
@Mbeaulne Mbeaulne force-pushed the 12-18-unify_status_better branch from 65cdf3c to adf56fd Compare December 19, 2025 21:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants