Internal sync. by kyessenov · Pull Request #100 · cel-expr/cel-cpp

kyessenov · 2020-11-25T01:08:31Z

Internal sync.

google-cla · 2020-11-25T01:08:52Z

We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google.
In order to pass this check, please resolve this problem and then comment @googlebot I fixed it.. If the bot doesn't comment, it means it doesn't think anything has changed.

ℹ️ Googlers: Go here for more info.

google-cla · 2020-11-25T01:09:00Z

We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google.
In order to pass this check, please resolve this problem and then comment @googlebot I fixed it.. If the bot doesn't comment, it means it doesn't think anything has changed.

ℹ️ Googlers: Go here for more info.

google-cla · 2020-11-25T01:09:08Z

We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google.
In order to pass this check, please resolve this problem and then comment @googlebot I fixed it.. If the bot doesn't comment, it means it doesn't think anything has changed.

ℹ️ Googlers: Go here for more info.

PiperOrigin-RevId: 336325540

Add type() builtin function implementation to CEL C++ evaluator. PiperOrigin-RevId: 336360964

…ateStruct` constructs. PiperOrigin-RevId: 336722378

PiperOrigin-RevId: 336772611

google-cla · 2020-11-25T01:11:55Z

We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google.
In order to pass this check, please resolve this problem and then comment @googlebot I fixed it.. If the bot doesn't comment, it means it doesn't think anything has changed.

ℹ️ Googlers: Go here for more info.

PiperOrigin-RevId: 337110846

google-cla · 2020-11-25T01:12:04Z

We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google.
In order to pass this check, please resolve this problem and then comment @googlebot I fixed it.. If the bot doesn't comment, it means it doesn't think anything has changed.

ℹ️ Googlers: Go here for more info.

PiperOrigin-RevId: 337131059

google-cla · 2020-11-25T01:12:13Z

We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google.
In order to pass this check, please resolve this problem and then comment @googlebot I fixed it.. If the bot doesn't comment, it means it doesn't think anything has changed.

ℹ️ Googlers: Go here for more info.

PiperOrigin-RevId: 337585239

google-cla · 2020-11-25T01:12:21Z

We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google.
In order to pass this check, please resolve this problem and then comment @googlebot I fixed it.. If the bot doesn't comment, it means it doesn't think anything has changed.

ℹ️ Googlers: Go here for more info.

PiperOrigin-RevId: 339080710

google-cla · 2020-11-25T01:12:30Z

We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google.
In order to pass this check, please resolve this problem and then comment @googlebot I fixed it.. If the bot doesn't comment, it means it doesn't think anything has changed.

ℹ️ Googlers: Go here for more info.

…ng easier. PiperOrigin-RevId: 339114639

google-cla · 2020-11-25T01:12:38Z

We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google.
In order to pass this check, please resolve this problem and then comment @googlebot I fixed it.. If the bot doesn't comment, it means it doesn't think anything has changed.

ℹ️ Googlers: Go here for more info.

google-cla · 2020-11-25T01:12:46Z

We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google.
In order to pass this check, please resolve this problem and then comment @googlebot I fixed it.. If the bot doesn't comment, it means it doesn't think anything has changed.

ℹ️ Googlers: Go here for more info.

…nstead of the pair ContainsMapKey/InsertOrLookupValue PiperOrigin-RevId: 339137778

PiperOrigin-RevId: 339520858

google-cla · 2020-11-25T01:12:59Z

We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google.
In order to pass this check, please resolve this problem and then comment @googlebot I fixed it.. If the bot doesn't comment, it means it doesn't think anything has changed.

ℹ️ Googlers: Go here for more info.

when the qualified enum id is encoded within an identifier and not just within parse-only select expressions. PiperOrigin-RevId: 340285064

google-cla · 2020-11-25T01:13:10Z

We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google.
In order to pass this check, please resolve this problem and then comment @googlebot I fixed it.. If the bot doesn't comment, it means it doesn't think anything has changed.

ℹ️ Googlers: Go here for more info.

PiperOrigin-RevId: 340749678

google-cla · 2020-11-25T01:13:19Z

We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google.
In order to pass this check, please resolve this problem and then comment @googlebot I fixed it.. If the bot doesn't comment, it means it doesn't think anything has changed.

ℹ️ Googlers: Go here for more info.

… of a receiver style Call expression before visiting any of the arguments. PiperOrigin-RevId: 342068658

google-cla · 2020-11-25T01:13:26Z

We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google.
In order to pass this check, please resolve this problem and then comment @googlebot I fixed it.. If the bot doesn't comment, it means it doesn't think anything has changed.

ℹ️ Googlers: Go here for more info.

PiperOrigin-RevId: 342177150

google-cla · 2020-11-25T01:13:35Z

We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google.
In order to pass this check, please resolve this problem and then comment @googlebot I fixed it.. If the bot doesn't comment, it means it doesn't think anything has changed.

ℹ️ Googlers: Go here for more info.

…esolving references. PiperOrigin-RevId: 342646217

google-cla · 2020-11-25T01:13:48Z

We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google.
In order to pass this check, please resolve this problem and then comment @googlebot I fixed it.. If the bot doesn't comment, it means it doesn't think anything has changed.

ℹ️ Googlers: Go here for more info.

Replace Enum idents that have constant value in the reference map with PiperOrigin-RevId: 343033308

google-cla · 2020-11-25T01:13:56Z

We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google.
In order to pass this check, please resolve this problem and then comment @googlebot I fixed it.. If the bot doesn't comment, it means it doesn't think anything has changed.

ℹ️ Googlers: Go here for more info.

This allows removal of gRPC dependency from cel-cpp workspace. PiperOrigin-RevId: 343346002

google-cla · 2020-11-25T01:14:09Z

We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google.
In order to pass this check, please resolve this problem and then comment @googlebot I fixed it.. If the bot doesn't comment, it means it doesn't think anything has changed.

ℹ️ Googlers: Go here for more info.

Minor fixes for OSS-compatible build. PiperOrigin-RevId: 344157853

google-cla · 2020-11-25T01:14:17Z

We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google.
In order to pass this check, please resolve this problem and then comment @googlebot I fixed it.. If the bot doesn't comment, it means it doesn't think anything has changed.

ℹ️ Googlers: Go here for more info.

google-cla · 2020-11-25T01:14:26Z

We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google.
In order to pass this check, please resolve this problem and then comment @googlebot I fixed it.. If the bot doesn't comment, it means it doesn't think anything has changed.

ℹ️ Googlers: Go here for more info.

google-cla Bot added the cla: yes CLA present label Nov 25, 2020

google-cla Bot added cla: no CLA not present and removed cla: yes CLA present labels Nov 25, 2020

Enable timestamp tests and add support for fixed timezones.

4dfaf39

PiperOrigin-RevId: 336325540

kyessenov force-pushed the cpp-sync branch from 9908ea8 to 4dfaf39 Compare November 25, 2020 01:11

google-cla Bot added cla: yes CLA present and removed cla: no CLA not present labels Nov 25, 2020

kmilsht and others added 3 commits November 24, 2020 20:11

Add support for CelType to FunctionAdapter.

85a8fe3

Add type() builtin function implementation to CEL C++ evaluator. PiperOrigin-RevId: 336360964

Makes CEL parser tolerate trailing commas in CreateMessage and `Cre…

5877e23

…ateStruct` constructs. PiperOrigin-RevId: 336722378

Internal change.

187e722

PiperOrigin-RevId: 336772611

google-cla Bot added cla: no CLA not present and removed cla: yes CLA present labels Nov 25, 2020

Fix signed and unsigned integer overflow cases within C++ evaluator.

6821237

PiperOrigin-RevId: 337110846

Enable proto2/proto3 test inputs for C++ Conformance server.

5efd741

PiperOrigin-RevId: 337131059

Internal change.

c20d88d

PiperOrigin-RevId: 337585239

Adding support for bool keys to FieldBackedMapImpl

729b8f3

PiperOrigin-RevId: 339080710

Print out the optional field name in NoSuchFieldError to make debuggi…

70b6812

…ng easier. PiperOrigin-RevId: 339114639

kmilsht and others added 2 commits November 24, 2020 20:12

Switch FieldBackedMapImpl to use proto2::Reflection::LookupMapValue i…

6dfb7c8

…nstead of the pair ContainsMapKey/InsertOrLookupValue PiperOrigin-RevId: 339137778

Clean up unused protobuf-lite dependency

5200c84

PiperOrigin-RevId: 339520858

Update the has() macro support for C++ and fix enum resolution behavior

4e2d9ae

when the qualified enum id is encoded within an identifier and not just within parse-only select expressions. PiperOrigin-RevId: 340285064

Add function reference renaming to reference resolver.

e541ad5

PiperOrigin-RevId: 340749678

Introduce PostVisitTarget() into the ast_visitor, to visit the target…

26599a1

… of a receiver style Call expression before visiting any of the arguments. PiperOrigin-RevId: 342068658

Allow disabling the check phase.

03d782f

PiperOrigin-RevId: 342177150

Add overloads for building checked exprs. Add rewriting routine for r…

dbe7c54

…esolving references. PiperOrigin-RevId: 342646217

Use Enum Const References

28cffc2

Replace Enum idents that have constant value in the reference map with PiperOrigin-RevId: 343033308

Implement a pipe protocol for cel-spec conformance client/server.

684848d

This allows removal of gRPC dependency from cel-cpp workspace. PiperOrigin-RevId: 343346002

Re-organize OSS build for easier maintenance.

fc02992

Minor fixes for OSS-compatible build. PiperOrigin-RevId: 344157853

kyessenov added cla: yes CLA present and removed cla: no CLA not present labels Nov 25, 2020

kyessenov changed the title ~~Enable timestamp tests and add support for fixed timezones.~~ Internal sync. Nov 25, 2020

kyessenov merged commit c804f26 into master Nov 25, 2020

kyessenov deleted the cpp-sync branch November 25, 2020 01:22

Uh oh!

Conversation

kyessenov commented Nov 25, 2020 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

google-cla Bot commented Nov 25, 2020

Uh oh!

google-cla Bot commented Nov 25, 2020

Uh oh!

google-cla Bot commented Nov 25, 2020

Uh oh!

google-cla Bot commented Nov 25, 2020

Uh oh!

google-cla Bot commented Nov 25, 2020

Uh oh!

google-cla Bot commented Nov 25, 2020

Uh oh!

google-cla Bot commented Nov 25, 2020

Uh oh!

google-cla Bot commented Nov 25, 2020

Uh oh!

google-cla Bot commented Nov 25, 2020

Uh oh!

google-cla Bot commented Nov 25, 2020

Uh oh!

google-cla Bot commented Nov 25, 2020

Uh oh!

google-cla Bot commented Nov 25, 2020

Uh oh!

google-cla Bot commented Nov 25, 2020

Uh oh!

google-cla Bot commented Nov 25, 2020

Uh oh!

google-cla Bot commented Nov 25, 2020

Uh oh!

google-cla Bot commented Nov 25, 2020

Uh oh!

google-cla Bot commented Nov 25, 2020

Uh oh!

google-cla Bot commented Nov 25, 2020

Uh oh!

google-cla Bot commented Nov 25, 2020

Uh oh!

google-cla Bot commented Nov 25, 2020

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

kyessenov commented Nov 25, 2020 •

edited

Loading