Skip to content

fix: handle optional 'description' in example registry server#32

Merged
mindpower merged 1 commit into
ards-project:mainfrom
x0cipher:fix/registry-server-optional-description
Jun 22, 2026
Merged

fix: handle optional 'description' in example registry server#32
mindpower merged 1 commit into
ards-project:mainfrom
x0cipher:fix/registry-server-optional-description

Conversation

@x0cipher

Copy link
Copy Markdown
Contributor

Hit this while poking at the conformance demo: description is 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 on entry.get("description", "") instead of entry["description"]
  • added a description-less entry to the mock catalog + examples/ai-catalog.json (kept in sync) so run-conformance-demo actually exercises the optional path

Before / after

  • before: manifest validation passes, but the /search probe dies with Remote end closed connection
  • after: demo's green end to end

@mindpower mindpower left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you @x0cipher for fixing this!

@mindpower mindpower merged commit 9e569d8 into ards-project:main Jun 22, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

2 participants