fix(registry): function names are canonical slugs — worker matches tensorhub dispatch vocabulary#46
Merged
Merged
Conversation
…nsorhub dispatch vocabulary
The platform's canonical function name is the slug (tensorhub
builder.NormalizeSlug, '_' -> '-'; the discovery manifest already
publishes it), but the runtime registry keyed specs by the raw python
attr name — so the orchestrator's RunJob.function_name ('marco-polo')
never matched the worker's advertised available_functions
('marco_polo') and every dispatch would come back INVALID. Slugify once
at spec extraction; the CLI accepts either spelling by slugifying
lookups. Found by e2e #100 S1 (first live contact of the two protocol
v2 implementations).
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
1 participant
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.
The platform's canonical function name is the slug (tensorhub
builder.NormalizeSlug, '_' -> '-'; the discovery manifest already
publishes it), but the runtime registry keyed specs by the raw python
attr name — so the orchestrator's RunJob.function_name ('marco-polo')
never matched the worker's advertised available_functions
('marco_polo') and every dispatch would come back INVALID. Slugify once
at spec extraction; the CLI accepts either spelling by slugifying
lookups. Found by e2e #100 S1 (first live contact of the two protocol
v2 implementations).