You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would expect that the react app, python server, and docs are consistent in how they implement or (for the docs) describe how the registry is ingested.
Python App: The python app appears to use get_registry_dump to produce a JSON dump of the registry, but get_registry_dump is never called. Instead the UI fetches the registry_proto from /registry (see here and here).
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Expected Behavior
I would expect that the react app, python server, and docs are consistent in how they implement or (for the docs) describe how the registry is ingested.
Current Behavior
Right now:
get_registry_dump
to produce a JSON dump of the registry, butget_registry_dump
is never called. Instead the UI fetches theregistry_proto
from/registry
(see here and here).useLoadRegistry
looks like it used to parse json -- as in feat: Initial merge of Web UI logic #2352 -- but then chore: Replace zod by protobufjs #3208 replaced thejson
with the protobuf registrySteps to reproduce
NA
Specifications
main
Possible Solution
If the intent of #3208 was to replace the json registry with the protobuf version, then the solution would be to:
ui_server
so it doesn't appear to produce the JSON dump viaget_registry_dump
Of these solutions, the first (updating docs) is probably the most valuable to the community.
The text was updated successfully, but these errors were encountered: