Reuse token cache until the server rejects it - #7
Merged
Conversation
Remove the creation-date gate from token cache loading so cached credentials can be reused across days. Refresh the access token only after an authenticated API request reports that it is invalid, while keeping signing-material cache expiry unchanged. Update CLI wording, user and agent documentation, security guidance, changelog entries, and regression tests for the new cache behavior. Validation: python -m ruff format --check .; python -m ruff check .; python -m pytest --cov (266 passed, 2 skipped, 78% coverage).
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.
Changes
401orcode=4000, then retry the original request.Validation
python -m ruff format --check .python -m ruff check .python -m pytest --cov(266 passed, 2 skipped, 78% coverage)CHANGELOG.mdTHIRD_PARTY_NOTICES.mddoes not require an updatedocs/OPEN_SOURCE_RELEASE.mdreview is requiredManual Testing
No real Huawei account or device was used. Unit tests cover reusing the Token cache, avoiding refresh after successful requests, and refreshing and retrying after server rejection.