Repository navigation
accept any jobs hardware flavor - #278
Merged
Merged
Conversation
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
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.
hf_jobsnow accepts any hardware flavor and leaves validation to the Jobs API. Before this, the flavor was a fixed list, so current hardware likeh200andrtx-pro-6000was rejected before the job reached the Hub:{ "operation": "run", "args": { "image": "python:3.12", "command": ["nvidia-smi"], "flavor": "h200" } }The known flavors are still listed in the param description and the help text as hints. They now match
GET /api/jobs/hardware, which adds the h200 and rtx-pro-6000 sizes and dropszero-a10g,sprx8andinf2x6(the Jobs API doesn't list those). A misspelled or unavailable flavor now comes back as the Jobs API's own error. New hardware no longer needs a schema change or an@huggingface/hubbump.