Skip to content
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 issue #543 : cached key set expiration are not handled #549

Closed
wants to merge 2 commits into from

Conversation

romain-neil
Copy link

Hello,

This PR aim to fix the issue #543 , as cached key set expiration', are not takken into account.

Thanks,

Copy link

google-cla bot commented Nov 29, 2023

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

Copy link
Collaborator

@bshaffer bshaffer left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for your contribution!

It looks like you're changing a lot of things that you don't need to. I would suggest only changing the things that require changing (instead of the larger refactor that you seem to have going on here).

@@ -20,7 +20,8 @@
],
"license": "BSD-3-Clause",
"require": {
"php": "^7.4||^8.0"
"php": "^7.4||^8.0",
"ext-json": "*"
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we do not want to introduce a new dependency in the library like this - it could change behavior for existing installations.

//Check keyId presence
if (!isset($keySet[$keyId])) {
return false;
}
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The whitespace is inconsistent, which makes this hard to review.

@bshaffer
Copy link
Collaborator

bshaffer commented Dec 1, 2023

As far as I can tell, the changes are completely unrelated to the linked issue. Also this PR is unreadable due to incorrect whitespace changes.

@bshaffer bshaffer closed this Dec 1, 2023
@romain-neil romain-neil deleted the fix-543 branch December 4, 2023 07:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants