Skip to content

FIX: distinguish catalog-unavailable from unregistered in Initializers page - #2464

Open
fei (feiiiiii5) wants to merge 1 commit into
microsoft:mainfrom
feiiiiii5:fix/initializer-catalog-unavailable
Open

FIX: distinguish catalog-unavailable from unregistered in Initializers page#2464
fei (feiiiiii5) wants to merge 1 commit into
microsoft:mainfrom
feiiiiii5:fix/initializer-catalog-unavailable

Conversation

@feiiiiii5

Copy link
Copy Markdown
Contributor

Description

Fixes #2442

When /api/initializers/settings succeeds but the registered-initializer catalog request (GET /api/initializers) fails transiently, the Initializers page preserved configured baseline settings but described valid entries as Initializer is no longer registered. A temporary metadata availability failure was therefore presented as a definitive registration problem.

Changes:

  • Initializers.tsx: track catalogUnavailable state — set to true when only the catalog request rejects, reset on success or refresh
  • BaselineInitializers.tsx / AdditionalInitializers.tsx: accept and forward the flag
  • initializerLookup.ts: when the catalog is unavailable, unresolved names render Catalog metadata temporarily unavailable. instead of the definitive fallback; names genuinely absent from a successful response still show no longer registered

Tests and Documentation

  • Added unit tests in initializerLookup.test.ts:
    • Returns a "temporarily unavailable" placeholder when catalogUnavailable=true
    • Still matches by name when the catalog is available (flag=false)
  • TypeScript type check passes: tsc --noEmit (0 errors)
  • No documentation changes needed (UI-only behavioral fix)

This contribution was developed with LLM assistance following repo conventions.

…s page

When the registered-initializer catalog request fails transiently, the
Initializers page preserved configured baseline settings but described
valid entries as 'Initializer is no longer registered.' A temporary
metadata availability failure was therefore presented as a definitive
registration problem.

Track catalog fetch success/failure and pass the availability flag
through to BaselineInitializers / AdditionalInitializers so unresolved
names render 'Catalog metadata temporarily unavailable.' when only the
catalog request failed. Names genuinely absent from a successful catalog
response still show 'no longer registered.'

Fixes microsoft#2442

Signed-off-by: fei <204683769+feiiiiii5@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Initializer catalog failure falsely marks configured entries as unregistered

1 participant