[Bug]: model registry validator accepts padded names and config IDs
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 14.7k
- Forks
- 2.8k
- Avg merge
- 2d 23h
- Merged PRs (30d)
- 489
Description
System Info
Platform-independent AutoDeploy registry validation.
Reproduction
validate_models() checks name and config_id with .strip() only to determine whether they are non-empty, but then retains the original untrimmed values. Entries such as name: "model" and name: "model ", or config_id: "default" and config_id: " default", therefore pass validation as distinct identifiers.
These invisible leading/trailing characters can bypass duplicate checks and later produce lookup mismatches.
Expected behavior
Registry identifiers should reject leading or trailing whitespace.
Actual behavior
Padded non-empty strings are accepted.
Proposed fix
Reject surrounding whitespace in name and config_id, with focused validator regression tests.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the validate_models() entry point and inspect the focused validator tests or their surrounding test module. Add regression coverage showing that leading or trailing whitespace in name and config_id is rejected; done means padded identifiers no longer pass validation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 72/100