Skip to content

Fix preflight for remote model and container aliases#201

Open
fallintoplace wants to merge 1 commit into
NVIDIA:mainfrom
fallintoplace:fix/preflight-resolved-remote-aliases
Open

Fix preflight for remote model and container aliases#201
fallintoplace wants to merge 1 commit into
NVIDIA:mainfrom
fallintoplace:fix/preflight-resolved-remote-aliases

Conversation

@fallintoplace
Copy link
Copy Markdown

Summary

  • accept model_paths aliases that resolve to hf: model IDs during preflight
  • accept containers aliases that resolve to remote image URIs during preflight
  • add regression coverage for both alias paths

Why

Preflight already accepts literal hf: model paths and literal remote container image URIs. It was checking the raw recipe values for those remote forms, though, so aliases that resolved to the same supported values were still checked as local paths/files and rejected before submission.

Test plan

  • PYTHONPATH=src uv run --no-project --with pytest --with pyyaml --with jinja2 --with marshmallow --with marshmallow-dataclass --with requests --with rich --with questionary --with ruamel.yaml --with pydantic --with mcp --with matplotlib -- python -m pytest tests/test_validation.py -v
  • uv run --no-project --with ruff -- ruff check src/srtctl/core/validation.py tests/test_validation.py

@fallintoplace fallintoplace marked this pull request as ready for review June 6, 2026 17:19
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