-
Notifications
You must be signed in to change notification settings - Fork 417
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
[Cherry-pick] Port CEL fixes for release v0.6.1 #665
Conversation
There was a bug in the handling of list results, where they weren't being marshaled correctly, resulting in an error. This change identifies list results, and marshals them accordingly. This also bumps the version of cel to the latest 0.5.1
compareSecret in both its forms was declared as returning a String not a Bool. This fixes both of these.
@bigkevmcd A unit test fails when I cherry-pick #652 . Any ideas on what to fix here? |
The following is the coverage report on the affected files.
|
t> @bigkevmcd A unit test fails when I cherry-pick #652 . Any ideas on what to fix here?
I ran into this earlier, and my gut feeling is that it's a bug in protojson, sometimes it puts a space between list elements in the JSON output, and sometimes it doesn't. Unfortunately the JSON marshaling that was used before is now deprecated, and the PR checks failed because of this. The Spaces clearly don't affect the parsing of the result, but lemme see if I can improve the parsing of the test. |
This is the issue golang/protobuf#1121 |
|
The following is the coverage report on the affected files.
|
The marshaled JSON output is flaky, this ensures that it matches after parsing.
The following is the coverage report on the affected files.
|
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 This pull-request has been approved by: wlynch 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 |
Changes
This cherry-picks two PRs for v0.6.1:
Submitter Checklist
These are the criteria that every PR should meet, please check them off as you
review them:
See the contribution guide for more details.