fix(keychain): recover transient session reads#25
Merged
Conversation
hubab1
force-pushed
the
16-keychain-read-recovery
branch
from
July 26, 2026 12:06
a2c8398 to
75e2d03
Compare
hubab1
marked this pull request as ready for review
July 26, 2026 12:06
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.
Summary
Verification
AppServicesDependencyTestspassedmaingit diff --checkpassedThe automated suite simulates locked/unavailable Keychain status codes. It does not lock the user's real login Keychain.
Attribution
Recovery behavior was independently implemented after reviewing Felix Lisczyk’s fork commit b05eb34. This version narrows retries to explicitly classified transient Keychain statuses and redacts item identifiers. No commits were cherry-picked.