fix: handle optional 'description' in example registry server#32
Merged
mindpower merged 1 commit intoJun 22, 2026
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.
Hit this while poking at the conformance demo:
descriptionis optional (§4.2), but the example registry assumes it's always there, so a valid catalog that omits it just 500s on/search. Small fix, but the demo never covered that path so I added a case for it too.What changed
registry-server.py: search matches onentry.get("description", "")instead ofentry["description"]examples/ai-catalog.json(kept in sync) sorun-conformance-demoactually exercises the optional pathBefore / after
/searchprobe dies withRemote end closed connection