Skip to content

feat(platform): add RTX_PRO_6000 to the GPUType enum - #720

Open
oatanas wants to merge 1 commit into
feat/PYSDK-133/integrationfrom
feat/HETA-1792-rtx-pro-6000-gpu-type-pysdk133
Open

feat(platform): add RTX_PRO_6000 to the GPUType enum#720
oatanas wants to merge 1 commit into
feat/PYSDK-133/integrationfrom
feat/HETA-1792-rtx-pro-6000-gpu-type-pysdk133

Conversation

@oatanas

@oatanas oatanas commented Sep 11, 2026

Copy link
Copy Markdown

Targets feat/PYSDK-133/integration. Supersedes #719, which was opened against main before I knew this was the integration target; #719 is closed. Re-applied by hand rather than cherry-picked, since this branch renames the package to src/aignostics_sdk/.

Summary

Adds RTX_PRO_6000 to platform.GPUType. The he-tme application already accepts RTX PRO 6000 (sm_120) GPUs for HETA-1792, but the SDK enum stopped at L4 and A100.

This is not only a CLI-help issue: Runs.submit() calls validate_run_sdk_metadata(custom_metadata["sdk"]) on every submission, which validates pipeline.gpu.gpu_type against this enum. Verified against the released SDK 1.4.9:

pipeline.gpu.gpu_type
  Input should be 'L4' or 'A100' [type=enum, input_value='RTX_PRO_6000', input_type=str]

Because the gate is inside submit(), and that method exposes no opt-out, a downstream caller cannot route around it — stargate's "pass unknown GPU types through" change (stargate#378) still failed here. Adding the member is the fix.

Schema version

Bumps SDK_METADATA_SCHEMA_VERSION to 0.0.7 and regenerates docs/source/_static/sdk_run_custom_metadata_schema_{v0.0.7,latest}.json. This follows the precedent of 0.0.6, which was bumped for the equivalent change of adding FLEX_START to the provisioning-mode enum. The change only widens what validates, so metadata written against 0.0.6 remains valid.

Deliberately not included

  • CLI_REFERENCE.md. It is generated and already drifted from the CLI on this branch; regenerating locally rewrites ~745 lines (a TEXT<str> typer formatting change, plus sections that disappear unless every extra is installed). It belongs in its own chore commit via nox -s docs.
  • Two unrelated lint fixes. ruff check auto-fixed an import-organization error in application/_cli.py and a blank-line issue in application/_service.py; both reproduce on this branch at HEAD without my change, so I reverted them to keep the diff minimal. Worth a separate cleanup.

Test plan

  • pytest tests/aignostics/platform/sdk_metadata_test.py -m unit — 71 passed
  • ruff check --no-fix / ruff format --check clean on the changed files
  • Regenerated schema contains "enum": ["L4", "A100", "RTX_PRO_6000"]

🤖 Generated with Claude Code

https://claude.ai/code/session_01CNyXyfHNFAgv7zUYjUG22P

The he-tme application accepts RTX PRO 6000 (sm_120) GPUs, but the SDK enum
stopped at L4 and A100, so `validate_run_sdk_metadata` — which `Runs.submit`
calls on every submission — rejected the run before it reached the platform:

    pipeline.gpu.gpu_type
      Input should be 'L4' or 'A100' [type=enum, input_value='RTX_PRO_6000']

That gate is inside the SDK and `submit` has no opt-out, so no caller could
work around it; passing the string through from a downstream CLI still failed
here.

Bumps SDK_METADATA_SCHEMA_VERSION to 0.0.7 and regenerates the published run
schema, following 0.0.6, which was bumped for the equivalent change (adding
FLEX_START to the provisioning-mode enum). Adding an enum member widens what
validates, so runs written against 0.0.6 stay valid.

CLI_REFERENCE.md is left alone: it is generated, has drifted from the current
CLI, and `nox -s docs` regenerates it with all extras installed.

Refs HETA-1792

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01CNyXyfHNFAgv7zUYjUG22P
@oatanas
oatanas requested a review from a team as a code owner September 11, 2026 11:35
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.

1 participant