-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
deps: update cel-cpp to 0.6.1 #16293
Conversation
Signed-off-by: Kuat Yessenov <[email protected]>
Signed-off-by: Kuat Yessenov <[email protected]>
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.
Would be could to switch to releases for cel-cpp and abseil if possible
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.
As per comments it would be preferable to switch to releases for both cel-cpp and abseil
/retest |
Retrying Azure Pipelines: |
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 deps
/retest |
Retrying Azure Pipelines: |
Signed-off-by: Kuat Yessenov <[email protected]>
Signed-off-by: Kuat Yessenov <[email protected]>
Signed-off-by: Kuat Yessenov <[email protected]>
/retest |
Retrying Azure Pipelines: |
Windows compiler does not like initializing int64_t constexpr with long values, sending a patch upstream. |
Signed-off-by: Kuat Yessenov <[email protected]>
This might require some serious patching of cel-cpp since it assumes aliased string_views when using protobuf. Sigh. |
@kyessenov is there any way to avoid Envoy-side patches? We're really trying to avoid these going forward. |
@htuch Yes, it can be fixed upstream. It's difficult to enforce in g3, so it just needs regular maintenance to ensure abseil-protobuf use is valid with non-aliased absl and std string_views. |
Signed-off-by: Kuat Yessenov <[email protected]>
Signed-off-by: Kuat Yessenov <[email protected]>
Thank you for identifying the ambiguous long vs int64 issue. Awaiting cleaning up format check |
/retest |
Retrying Azure Pipelines: |
The coverage dropped by 0.1% because of dependency upgrade? That is unexpected. |
/retest |
Retrying Azure Pipelines: |
/retest |
Retrying Azure Pipelines: |
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 /deps ... Unconcerned about third party code coverage
/lgtm deps |
/retest |
Retrying Azure Pipelines: |
Yay, took 2 months on-off but finally ready! |
* main: listener: match rebalancer to listener IP family type (envoyproxy#16914) jwt_authn: implementation of www-authenticate header (envoyproxy#16216) listener: reset the file event in framework instead of listener filter doing itself (envoyproxy#17227) Small typo fix (envoyproxy#17247) Doc: Clarify request/response attributes are http-only (envoyproxy#17204) bazel/README.md: add aspell comment (envoyproxy#17072) docs: Fix broken URL links in HTTP upgrades doc (envoyproxy#17225) remove the wrong comment on test (envoyproxy#17233) upstream: allow clusters to skip waiting on warmup for initialization (envoyproxy#17179) JwtAuthn: support completing padding on forward jwt payload header (envoyproxy#16752) remove support for v2 UNSUPPORTED_REST_LEGACY (envoyproxy#16968) metrics service: fix wrong argument arrange on MetricsServiceSink (envoyproxy#17127) deps: update cel-cpp to 0.6.1 (envoyproxy#16293) Add ability to filter ConfigDump. (envoyproxy#16774) examples: fix Wasm example. (envoyproxy#17218) upstream: update host's socket factory when metadata is updated. (envoyproxy#16708) Signed-off-by: Garrett Bourg <[email protected]>
Signed-off-by: Kuat Yessenov <[email protected]> Signed-off-by: chris.xin <[email protected]>
Signed-off-by: Kuat Yessenov <[email protected]>
Signed-off-by: Kuat Yessenov [email protected]
Commit Message: update CEL evaluator to latest release
Risk Level: low
Testing: unit / regression
Docs Changes: none
Release Notes: none