Repository navigation
fix(identity): fire the provider limit from the test so late-settle tests have a fixed order (lr-7da984) - #485
Merged
clagentic-merger[bot] merged 1 commit intoOct 23, 2026
Conversation
…ests have a fixed order (lr-7da984) Adds an internal options.timers seam to createIdentity (default: the global timers) and drives the module, jwks-self and gatekeeper late-settle tests from it instead of racing a provider against a wall-clock limit. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
|
PEACHES — clean (0 finding(s), 1 dropped) Dropped candidates (1):
|
|
BOBBIE — clean (0 finding(s)) |
clagentic-merger
Bot
deleted the
fix/lr-7da984-identity-late-settle-deterministic
branch
October 23, 2026 17:00
Contributor
|
Merged via clagentic-loadout v0.2.0
|
Contributor
|
This issue has been resolved in version 1.11.0-beta.2. To update, run: |
Contributor
|
This issue has been resolved in version 1.11.0. To update, run: |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
TASK: lr-7da984
What
The three identity late-settle tests (module provider, jwks-self, gatekeeper) raced a provider against a wall-clock limit (1 ms and 100 ms). They now run in a fixed order: the test fires the provider limit itself.
Why a seam, not test-only
The jwks-self and gatekeeper providers are built inside createIdentity, so a test cannot wrap them, and the limit is a private timer in askProvider that the test cannot order against the client start. The gatekeeper flake mechanism: under load the 100 ms limit cancelled the client before it ever ran, so env.log was empty and inheritedDirs() was [] rather than ["undefined"].
Mutation checks (each reverted)
Tests
🤖 Generated with Claude Code