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 index out of range panic when annotation is not in 'key=value' format #764
🐛 fix index out of range panic when annotation is not in 'key=value' format #764
Conversation
e419c12
to
7c7b6ee
Compare
Code changes look ok, are there any test cases for the annotation marker that we can update to make sure this is working as expected/we don't regress in the future? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That shows great 🥇
/lgtm
|
7c7b6ee
to
9fc6970
Compare
@JoelSpeed I've add some test cases to cover, PTAL, thanks! |
3ff3df6
to
9c90660
Compare
9c90660
to
aaf1431
Compare
aaf1431
to
6675a05
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED Approval requirements bypassed by manually added approval. This pull-request has been approved by: camilamacedo86, lianghao208 The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
When using
#691 in CRD struct files to generate api-approved annotation, if the annotation is not in
metadata:annotations:"xxx=xxx"
format, eg:it triggers index out of range panic.