Skip to content

fix(sdk): sanitize generated Harbor job names#1031

Draft
xdlkc wants to merge 1 commit into
alibaba:masterfrom
xdlkc:feature/harbor-job-name-sanitize
Draft

fix(sdk): sanitize generated Harbor job names#1031
xdlkc wants to merge 1 commit into
alibaba:masterfrom
xdlkc:feature/harbor-job-name-sanitize

Conversation

@xdlkc
Copy link
Copy Markdown
Contributor

@xdlkc xdlkc commented May 27, 2026

Summary

  • reject explicit Harbor job_name values that contain /
  • strip path-like prefixes from dataset names and single task names when generating default Harbor job names

Why

Harbor job names are used as flat identifiers and path components in downstream job handling. Preserving slash-separated dataset/task identifiers can produce path-like job names and break consumers that expect a single flat name segment.

Fixes #1030

Validation

  • git diff --check
  • /Users/keluo/Code/rock-keluo/.venv/bin/python -m pytest tests/unit/sdk/job/test_config.py::TestHarborJobConfigAutoJobName -q -> 4 passed
  • manual Python check for suite/my-dataset + group/my-task generation and bad/name validation

Reject explicit Harbor job names containing path separators and strip dataset/task prefixes when auto-generating names.

Co-Authored-By: Codex <noreply@openai.com>

AI-Model: GPT-5 Codex

AI-Contributed/Feature: 6/6

AI-Contributed/UT: 0/0
@xdlkc xdlkc force-pushed the feature/harbor-job-name-sanitize branch from b28ccf7 to a748293 Compare May 28, 2026 04:14
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.

Harbor job name should reject path separators and sanitize generated names

1 participant