Skip to content

fix(platform): preserve newer default credential reads - #4641

Merged
yannickmonney merged 1 commit into
mainfrom
fix/provider-default-cache-generation
Oct 9, 2026
Merged

yannickmonney merged 1 commit into
mainfrom
fix/provider-default-cache-generation

Conversation

@yannickmonney

Copy link
Copy Markdown
Contributor

When a default-credential read fails after invalidation has already loaded a newer result, its rejection currently removes that newer cached result. Keep failed-read eviction limited to the Promise that is still current for that organization.

Add regression coverage for the delayed failure, distinct organization values, and refreshed values after invalidation. Record the automated coverage and its limits in the manual test register.

Validation: the new delayed-failure test fails against the previous implementation (3 queries instead of 2); all 77 provider-credential tests pass with the repair. Configured TypeScript import-closure checking, typed lint, formatting, scoped full-rule SAST and the five manual-test trees pass. Independent review passed. These checks do not claim a full monorepo run, a real broker database mutation, or measured production latency.

Follows the review of #4595 and native task TALE-1388.

@yannickmonney
yannickmonney force-pushed the fix/provider-default-cache-generation branch from f2250e1 to a4eb9d0 Compare October 9, 2026 10:15
@yannickmonney
yannickmonney merged commit e5d8b81 into main Oct 9, 2026
12 checks passed
@yannickmonney
yannickmonney deleted the fix/provider-default-cache-generation branch October 9, 2026 11:33
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