-
Notifications
You must be signed in to change notification settings - Fork 423
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix credential expirability check #777
base: master
Are you sure you want to change the base?
Fix credential expirability check #777
Conversation
Welcome @kanwren! |
Hi @kanwren. Thanks for your PR. I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
1502060
to
17498b2
Compare
@kanwren can you fix this also
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: kanwren The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
d702a81
to
df21a7d
Compare
df21a7d
to
b1aba1b
Compare
/ok-to-test |
fad4e03
to
fd5f0fe
Compare
Fixes a bug introduced during the refactor in e92213c, which incorrectly inverted the previous credential expirability checking logic. This caused errors about being unable to cache otherwise cachable credentials. Also changes the error log around the previous expirability check site to no longer log the error that previously came from the `ExpiresAt()` check; since this is now the wrong `err`, it's always `nil`. Addresses kubernetes-sigs#776
fd5f0fe
to
4b9d665
Compare
/lgtm |
Fixes a bug introduced during the refactor in e92213c, which incorrectly inverted the previous credential expirability checking logic. This caused errors about being unable to cache otherwise cachable credentials. Also changes the error log around the previous expirability check site to no longer log the error that previously came from the
ExpiresAt()
check; since this is now the wrongerr
, it's alwaysnil
.Addresses #776