feat:Add aborted status to prediction and training enums

[HavenDV]

Summary by CodeRabbit

• New Features
  • Introduced "aborted" as a new status state for predictions and training jobs, enabling more granular job lifecycle tracking.
  • Enhanced status descriptions to provide clearer guidance on the distinction between "canceled" and "aborted" states.

[coderabbitai]

Walkthrough

Updated the OpenAPI specification to add an "aborted" status value to both prediction and training status enums. Added descriptive text clarifying the meanings of "canceled" and "aborted" states in the status property documentation.

Changes

Cohort / File(s)	Summary
Status enum and description updates src/libs/Replicate/openapi.yaml	Added aborted to status enum for both schemas_prediction_response and schemas_training_response. Updated status property descriptions to clarify canceled and aborted states.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

• feat:Add 200 response to prediction POST endpoints; fix 'endpoint' typos #124: Updates the same schemas_prediction_response schema by adding 200 responses, which will now include the newly documented status values.

Poem

🐰 A status aborted, now clearer and bright,
No more confusion on cancels and flight,
Two schemas aligned with descriptive care,
The API now knows when to stop mid-air! 🚀

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Title Check	⚠️ Warning	The pull request title "feat:@coderabbitai" does not meaningfully describe the actual changes in the changeset. The raw summary shows that the pull request adds a new "aborted" status value to prediction and training status enums and augments status properties with descriptive text in the OpenAPI schema file. The title appears to be incomplete or bot-generated, containing only a feature prefix and a mention reference without conveying any information about what was actually changed. A developer scanning the git history would be unable to understand the purpose or scope of these changes based on this title alone.	The title should be revised to clearly describe the main change. A more appropriate title would be something like "Add 'aborted' status to prediction and training response schemas" or "Update OpenAPI schema with aborted status enum and descriptions". This would provide clarity about the actual modifications made to the OpenAPI specification file.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch bot/update-openapi_202510230109

---

📜 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 b7aaf05 and 270282a.

⛔ Files ignored due to path filters (4)

• src/libs/Replicate/Generated/Replicate.Models.SchemasPredictionResponse.g.cs is excluded by !**/generated/**
• src/libs/Replicate/Generated/Replicate.Models.SchemasPredictionResponseStatus.g.cs is excluded by !**/generated/**
• src/libs/Replicate/Generated/Replicate.Models.SchemasTrainingResponse.g.cs is excluded by !**/generated/**
• src/libs/Replicate/Generated/Replicate.Models.SchemasTrainingResponseStatus.g.cs is excluded by !**/generated/**

📒 Files selected for processing (1)

• src/libs/Replicate/openapi.yaml (2 hunks)

🔇 Additional comments (2)

src/libs/Replicate/openapi.yaml (2)

1544-1553: Status enum and documentation update looks good.

The addition of the aborted status value is well-documented. The description clearly distinguishes between canceled (terminated during/after running) and aborted (terminated before starting), which helps API consumers understand the different terminal states.

---

1741-1750: Consistent update to training status schema.

The training schema changes mirror the prediction schema updates, maintaining semantic consistency across both entities. The description appropriately documents the distinction between canceled and aborted states for trainings as well.

---

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

_{Comment @coderabbitai help to get the list of available commands and usage tips.}