Skip to content

fix(deps): AUT-2660 pin leptonai to 0.27.3 - #682

Open
svcnemo-autobot wants to merge 2 commits into
NVIDIA-NeMo:mainfrom
svcnemo-autobot:fix/pin-leptonai-0.27.3
Open

svcnemo-autobot wants to merge 2 commits into
NVIDIA-NeMo:mainfrom
svcnemo-autobot:fix/pin-leptonai-0.27.3

Conversation

@svcnemo-autobot

Copy link
Copy Markdown
Contributor

Background

Pin the Lepton AI SDK to the requested version instead of allowing unrestricted upgrades.

What changed

  • Set leptonai==0.27.3 and regenerate uv.lock without unrelated version changes.
  • Require an explicit mount storage source, as required by this SDK version.
  • Update Lepton/Ray fixtures and executor documentation; add missing-source regression coverage.

Details

SDK comparison confirmed that Mount.from_ changed from optional to required. Existing mounts must include from with their storage source.

flowchart LR
  A[leptonai 0.27.3] --> B[Required mount source]
  B --> C[Executor validation]
  B --> D[Lepton and Ray fixtures]
  B --> E[Configuration examples]
Loading

Tested

  • uv lock --check using uv 0.8.22: passed.
  • Repository Ruff lint and format checks: passed.
  • pytest test/core/execution/test_lepton.py test/run/ray/test_lepton.py: 91 passed.
  • Full coverage suite: 1711 passed, 5 failed, 25 errors, 1 deselected, 1 xfailed. Remaining failures concern unavailable Docker access, temporary Git fixture signing, and subprocesses without a home directory. The full suite did not pass locally.
  • Example scripts reported a child import error; no full example-validation claim.
  • Hosted installation matrix and remaining GitHub checks are pending.

Require explicit Lepton mount storage sources to match the SDK schema. Update executor examples and Lepton/Ray test fixtures, with regression coverage for missing sources.

Signed-off-by: svcnemo-autobot <svcnemo-autobot@nvidia.com>
@copy-pr-bot

copy-pr-bot Bot commented Oct 28, 2026

Copy link
Copy Markdown

This pull request requires additional validation before any workflows can run on NVIDIA's runners.

Pull request vetters can view their responsibilities here.

Contributors can view more details about this message here.

@svcnvidia-nemo-ci

Copy link
Copy Markdown
Contributor

/ok to test 777ae1d

@svcnvidia-nemo-ci svcnvidia-nemo-ci left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No merge-blocking defects found in this light review of all six changed files and their directly affected paths.

The dependency pin matches the lockfile. Mount validation, core/Ray fixtures, and documentation consistently require an explicit storage source. Traced mount propagation through data movement, job creation, and Ray head/worker specifications.

Static inspection only; tests and dependency resolution were not executed, and external SDK source was unavailable. Dependency review was completed directly because its delegated report was unavailable.

Review generated by codex. This was a full review. Request a full review with /review reset=true.

Signed-off-by: svcnemo-autobot <svcnemo-autobot@nvidia.com>

This branch was successfully deployed

1 active (outdated) deployment
public — 777ae1d3 Deployed Oct 28, 2026 by copy-pr-bot[bot] via release / finalize / notify #473
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants