Repository navigation
Conversation
DelegationCache gains a TTL'd per-bucket action set alongside the delegation index. Permits reports whether a cached set allows an action and whether a set is cached at all, so a caller with no set defers to Hilt instead of deciding. The set is keyed by the bucket DID Hilt named and lives in the same per-access-key store as the chains, so an invalidation drops both. No caller yet; the fast path starts consulting it in the next change. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Contributor
Author
|
Opened by mistake by a stack re-submit; this branch's PR #132 was already closed as superseded by the per-key marker design in fil-one/RFC#30 (f61f474). Branch kept. |
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
1 participant
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.
DelegationCache gains a TTL'd per-bucket action set alongside the
delegation index. Permits reports whether a cached set allows an action
and whether a set is cached at all, so a caller with no set defers to
Hilt instead of deciding. The set is keyed by the bucket DID Hilt named
and lives in the same per-access-key store as the chains, so an
invalidation drops both.
No caller yet; the fast path starts consulting it in the next change.
Co-Authored-By: Claude Fable 5.1 noreply@anthropic.com
Stack created with GitHub Stacks CLI • Give Feedback 💬