Removing a registered or subscribed service leaves stale local metadata After a…
- User
Removing a registered or subscribed service leaves stale local metadata
After a successful unregister or unsubscribe operation, the corresponding provider or consumer URL must no longer participate in local metadata, service matching, or revision calculation. Removing one URL must preserve unrelated registrations. If the remote operation fails, local metadata must not be removed as though the operation succeeded.
Interface
Type: Function Name: RemoveService Path: metadata/metadata.go Input: registryId string, url *common.URL Output: (no return value) Description: Removes a provider service URL from the local metadata for the given registry. Use this during unregister flows to keep the in-memory application-level metadata consistent with the actual exported services.
Type: Function Name: RemoveSubscribeURL Path: metadata/metadata.go Input: registryId string, url *common.URL Output: (no return value) Description: Removes a subscribed service URL from the local metadata for the given registry. Use this during unsubscribe flows to ensure stale subscribed URLs are cleaned from the application-level metadata.
- Assistant
Inspecting metadata handling and unregister/unsubscribe flows in the repository.
- Assistant
Implementing metadata removal functions and wiring them into unregister/unsubscribe flows.
- Assistant
Summary
Stale in-memory metadata after unregister/unsubscribe is fixed by mirroring the existing
AddService/AddSubscribeURLAPIs and calling them only after remote operations succeed.metadata/metadata.goRemoveService(registryId, url)— delegates toMetadataInfo.RemoveServicewhen that registry’s metadata exists (drops the provider URL from services and exported URLs).RemoveSubscribeURL(registryId, url)— same pattern for subscribed consumer URLs.
registry/servicediscovery/service_discovery_registry.goUnRegisterService— after each successfulserviceDiscovery.Unregister, removes the matching exported URL from local metadata (matched by instance ID / URL address). Failed unregisters leave metadata unchanged.UnRegister— on full success ofUnRegisterService, also callsmetadata.RemoveServicefor the URL being unregistered.UnSubscribe— after successfulserviceNameMapping.Remove, callsmetadata.RemoveSubscribeURL.
Behavior matches the requirements: metadata is updated only on success, one URL is removed without touching others, and failed remote calls do not clear local state.
Checks:
go test ./metadata/... ./registry/servicediscovery/...passed;git diff --checkclean; production diff is 2 files, +35 lines.
Other models, same or similar prompt
Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.
Identical first prompt
- composer-2.5Compare side by side →
- composer-2.5Compare side by side →
- composer-2.5Compare side by side →
- composer-2.5Compare side by side →
- gpt-5.6-solCompare side by side →
- gpt-5.6-solCompare side by side →
- gpt-5.6-solCompare side by side →
- gpt-5.6-solCompare side by side →
- gpt-5.6-solCompare side by side →
- fable-5Compare side by side →
- fable-5Compare side by side →