Jash Gulabrai 45e08ff417 fix: Handle case when Customizer Job status is unknown (#1965) ... # What does this PR do? This PR handles the case where a Customization Job's status is `unknown`. Since we don't map `unknown` to a valid `JobStatus`, the PostTraining provider throws an exception when fetching/listing a job. [//]: # (If resolving an issue, uncomment and update the line below) [//]: # (Closes #[issue-number]) ## Test Plan [Describe the tests you ran to verify your changes with result summaries. *Provide clear instructions so the plan can be easily re-executed.*] `./scripts/unit-tests.sh tests/unit/providers/nvidia/test_supervised_fine_tuning.py` succeeds [//]: # (## Documentation) Co-authored-by: Jash Gulabrai <jgulabrai@nvidia.com>		2025-04-17 10:27:07 +02:00
..
cli	refactor: tests/unittests -> tests/unit; tests/api -> tests/integration	2025-03-04 09:57:00 -08:00
distribution	fix(build): always pass path when no template/config provided (#1982)	2025-04-17 10:20:43 +02:00
models	feat: support '-' in tool names (#1807)	2025-04-12 14:23:03 -07:00
providers	fix: Handle case when Customizer Job status is unknown (#1965)	2025-04-17 10:27:07 +02:00
rag	chore: Get sqlite_vec and vector_store unit tests passing (#1413)	2025-03-05 13:20:13 -05:00
registry	fix: handle registry errors gracefully (#1732)	2025-03-20 15:24:07 -07:00
server	feat(server): add attribute based access control for resources (#1703)	2025-03-19 21:28:52 -07:00