Skip to content

Evict rejected WRD metadata loads without discarding newer refreshes - #135

Open
RichardHoekstra wants to merge 1 commit into
WebHare:mainfrom
RichardHoekstra:github/fix/wrd-rejected-metadata-cache
Open

RichardHoekstra wants to merge 1 commit into
WebHare:mainfrom
RichardHoekstra:github/fix/wrd-rejected-metadata-cache

Conversation

@RichardHoekstra

Copy link
Copy Markdown
Contributor

Problem

WRDSchemaType.__ensureSchemaData() retains a rejected loading promise. Later requests receive the cached failure instead of loading metadata again.

Change

On rejection, clear the cache only if it still holds that loading promise. Preserve a newer refresh and rethrow the original error. The failed request is not automatically retried.

Validation

  • wrd.nodejs.test_wrd_cache_failures: fails before, passes after. Covers recovery and an older failed load racing a newer successful refresh.
  • Existing metadata tests, TypeScript compilation and unchanged ESLint checks pass.

Validated on the official 6.2 image for GitHub main a91a7a28, with the candidate sources installed. Full upstream CI has not been run.

@RichardHoekstra
RichardHoekstra requested a review from a team October 27, 2026 15:41

This branch was successfully deployed

1 active deployment
external-ci — c83fe3ab Deployed Oct 27, 2026 by RichardHoekstra via setup #198
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.

1 participant