fix(sdk): warn user of job name collision#36
Merged
Conversation
tejapulagam
force-pushed
the
warn-job-name
branch
from
July 22, 2026 20:38
7f34732 to
75850e1
Compare
tejapulagam
changed the title
tejapulagam
changed the title
lianakoleva
approved these changes
Jul 23, 2026
justusschock
approved these changes
Jul 23, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
When a job name is already taken, the backend silently creates the job under a suffixed name. Users who reuse their original name then point at the wrong/nonexistent job.
Job._submitnow emits a UserWarning when the created name differs from the requested one, showing both names and pointing to job.name. CoversJob.run, the CLI, and studio submissions.