Fix: Mini task page graphs were missing Timed out and Expired

[matt-aitken]

The mini graphs we show on the Tasks page weren't showing Timed out or Expired. These statuses were added elsewhere but not assigned a bar + color here… 🤦

Summary by CodeRabbit

• New Features
  • Enhanced the task activity chart by adding visual indicators for expired and timed-out events, providing more detailed insights into task performance.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 17186b3

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[coderabbitai]

Walkthrough

The changes update the TaskActivityGraph function by adding two new <Bar> components to the existing bar chart. These new bars represent the task activity states for EXPIRED and TIMED_OUT with a defined color, stack ID, stroke width, and bar size. The update only expands the displayed metrics without modifying the existing functionality or data flow.

Changes

File(s)	Change Summary
apps/webapp/app/routes/.../route.tsx	Added two <Bar> components in TaskActivityGraph for EXPIRED and TIMED_OUT status, with fill #F43F5E, stackId: a, strokeWidth: 0, and barSize: 10.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant TaskActivityGraph
    participant BarChart
    participant BarComponent

    User->>TaskActivityGraph: Request task activity chart
    TaskActivityGraph->>BarChart: Initialize chart rendering
    BarChart->>BarComponent: Render existing bars
    TaskActivityGraph->>BarComponent: Add Bar (EXPIRED) with properties (#F43F5E, stackId: a, strokeWidth: 0, barSize: 10)
    TaskActivityGraph->>BarComponent: Add Bar (TIMED_OUT) with properties (#F43F5E, stackId: a, strokeWidth: 0, barSize: 10)
    BarComponent-->>TaskActivityGraph: Return rendered bar components
    TaskActivityGraph->>User: Return complete chart

Loading

Poem

I hop through code with gleeful cheer,
New bars now add details so clear.
"EXPIRED" and "TIMED_OUT" join the play,
Filling the chart in a vibrant way.
A little hop of joy for every commit,
CodeRabbit sings—let's celebrate it! 🐇

Tip

⚡💬 Agentic Chat (Pro Plan, General Availability)

• We're introducing multi-step agentic chat in review comments and issue comments, within and outside of PR's. This feature enhances review and issue discussions with the CodeRabbit agentic chat by enabling advanced interactions, including the ability to create pull requests directly from comments and add commits to existing pull requests.

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between adbc7b4 and 17186b3.

📒 Files selected for processing (1)

• apps/webapp/app/routes/_app.orgs.$organizationSlug.projects.$projectParam.env.$envParam._index/route.tsx (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (5)

• GitHub Check: e2e / 🧪 CLI v3 tests (windows-latest - pnpm)
• GitHub Check: e2e / 🧪 CLI v3 tests (windows-latest - npm)
• GitHub Check: typecheck / typecheck
• GitHub Check: units / 🧪 Unit Tests
• GitHub Check: Analyze (javascript-typescript)

🔇 Additional comments (1)

apps/webapp/app/routes/_app.orgs.$organizationSlug.projects.$projectParam.env.$envParam._index/route.tsx (1)

548-549: Good addition of missing task states.

The changes correctly add visual representation for the EXPIRED and TIMED_OUT task states to the TaskActivityGraph component. This ensures that all task states are now properly displayed in the mini graphs on the Tasks page, fixing the issue mentioned in the PR objectives.

The styling (fill color, stackId, strokeWidth, barSize) is consistent with other error states, maintaining visual coherence in the UI.

✨ Finishing Touches

• 📝 Generate Docstrings

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai plan to trigger planning for file edits and PR creation.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.