fix: display abort status for aborted run

[RohitR311]

What this PR does? It displays the abort status for the run that is aborted.

Fixes: #526

Summary by CodeRabbit

• New Features
  • Introduced a new “aborted” run status that enhances feedback across the app with clear, localized labels in German, English, Spanish, Japanese, and Chinese.
  • The update enhances the visual display of run statuses, ensuring users can easily distinguish an intentionally halted run from other outcomes.

[coderabbitai[bot]]

Walkthrough

This pull request adds a new status key, "aborted", with corresponding translations to multiple locale files (German, English, Spanish, Japanese, and Chinese). In addition, the CollapsibleRow component now includes a conditional statement that renders a Chip component when the run status is "aborted". These changes ensure that the aborted status is properly localized and visibly rendered in the user interface without modifying the existing statuses.

Changes

File(s)	Change Summary
public/locales/de.json, public/locales/en.json, public/locales/es.json, public/locales/ja.json, public/locales/zh.json	Added new translation entry for the "aborted" status (values: "Abgebrochen", "Aborted", "Abortado", "中止されました", "已中止") in the run statuses section.
src/components/run/ColapsibleRow.tsx	Added a conditional rendering branch to display a Chip with the localized label when row.status equals "aborted".

Sequence Diagram(s)

sequenceDiagram
    participant U as User
    participant CR as CollapsibleRow Component
    participant T as Translation Module
    participant UI as UI Renderer

    U->>CR: Load run data (status "aborted")
    CR->>T: Request translation for "aborted"
    T-->>CR: Return localized label
    CR->>UI: Render Chip with "aborted" label
    UI-->>U: Display run status Chip

Assessment against linked issues

Objective	Addressed	Explanation
Aborted run status now displays correctly (#526)	✅

Poem

I'm a bunny with a coding heart,
Hopping through files and locales to chart,
Added "aborted" to our status array so fine,
Now every run reflects its design.
With a little hop and a joyful chirp,
I celebrate changes with a carrot "yip!"
🐰💻✨

---

📜 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 f4a75b590e1bace45ea07492887802433251d630 and edbf16529aa4f50a1ab4702010c08c7d838b0f98.

📒 Files selected for processing (6)

• public/locales/de.json (1 hunks)
• public/locales/en.json (1 hunks)
• public/locales/es.json (1 hunks)
• public/locales/ja.json (1 hunks)
• public/locales/zh.json (1 hunks)
• src/components/run/ColapsibleRow.tsx (1 hunks)

🔇 Additional comments (6)

public/locales/ja.json (1)

517-518: Added proper Japanese localization for aborted status.

The translation "中止されました" correctly captures the meaning of "aborted" in Japanese, complementing the existing status labels.

public/locales/de.json (1)

516-517: Added proper German localization for aborted status.

The translation "Abgebrochen" correctly captures the meaning of "aborted" in German, completing the set of status labels.

public/locales/zh.json (1)

517-518: Added proper Chinese localization for aborted status.

The translation "已中止" correctly captures the meaning of "aborted" in Chinese, maintaining consistency with other status translations.

public/locales/es.json (1)

517-518: Added proper Spanish localization for aborted status.

The translation "Abortado" correctly captures the meaning of "aborted" in Spanish, completing the localization for all run statuses.

src/components/run/ColapsibleRow.tsx (1)

128-128: Added UI display for aborted status.

The implementation correctly adds a conditional rendering for the "aborted" status with appropriate styling - using error color to visually indicate a terminated run. This matches the styling for other non-successful states and maintains UI consistency.

public/locales/en.json (1)

524-525: Add "aborted" status key: The new "aborted": "Aborted" entry is correctly added to the "run_status_chips" object, which will allow the UI to display the abort status for runs that have been aborted. Ensure that similar updates are consistently applied across all locale files to maintain proper localization.

✨ Finishing Touches

• [ ] 📝 Generate Docstrings

---

🪧 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.